Performance Bottleneck Diagnosis
Analyzes slow code for algorithmic and I/O hotspots, estimates complexity, and proposes measurable optimizations.
Prompt
ROLE: You are a performance engineer who optimizes only after measuring and reasoning about complexity. CONTEXT: The function/endpoint below is slow. Observed behavior: [LATENCY_OR_THROUGHPUT_NUMBERS] on input size [N]. Hot path runs [FREQUENCY]. Environment: [LANGUAGE/RUNTIME, HARDWARE_OR_CLOUD]. CODE: [PASTE_CODE] TASK: 1. State the current time and space complexity in Big-O, justifying it from the loops/calls in the code. 2. Identify the dominant bottleneck (algorithmic, allocation, I/O, N+1 queries, serialization, lock contention). 3. Propose 2-3 optimizations ranked by expected impact vs implementation cost; predict the new complexity for each. 4. Provide the optimized implementation for the top recommendation. 5. Specify exactly what to measure to confirm the win (metric, tool, expected delta). OUTPUT FORMAT: - 'Current cost' (complexity + suspected hotspot). - 'Optimization options' (table: option | expected gain | cost/risk). - 'Recommended implementation' (code). - 'Verification plan' (what to benchmark and how). CONSTRAINTS: Do not micro-optimize before fixing algorithmic issues. Preserve correctness and current behavior exactly; flag any change in semantics. Avoid premature caching unless data access patterns justify it. Cite the line(s) responsible for the bottleneck.
How to use this prompt
- 1
Copy the prompt above and paste it into ChatGPT, Claude, or Gemini — or open it in the visual Studio to edit each part on a canvas and run it with your own key.
- 2
Replace any bracketed placeholders with your specifics. The more concrete your context and constraints, the sharper the result — see the 5-part prompt structure.
- 3
Run it, then refine. Ask the model to critique and improve its own answer with self-critique prompting.
Techniques in this prompt
Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.
Learn this techniqueRecommended models
Build on this prompt
Open it in the visual Studio to wire it into a full workflow with your own API key — or learn the craft behind prompts like this.
More in Code Review & Debugging
Pull Request Review With Severity Triage
Reviews a pull request diff and returns issues bucketed by blocking, major, minor, and nit severity with concrete fixes.
Root-Cause Analysis From a Stack Trace
Walks a stack trace and surrounding code step by step to isolate the true root cause and propose a minimal verified fix.
Security-Focused Code Audit
Audits a code module against the OWASP Top 10 and common weakness patterns, reporting exploitability and remediation.
Concurrency And Race Condition Hunter
Inspects multithreaded or async code for races, deadlocks, and visibility bugs and proposes safe synchronization.