Prompt · Developer Tools

Profile Analyzer

Reads profiler output and identifies the real bottleneck, not just the hottest frame.

Have ready: Paste profiler output or describe the slow endpoint and its timings

Fill in · 4 fields

PASTE FLAMEGRAPH SUMMARY, pprof TOP, OR ENDPOINT TIMINGSENDPOINT / JOB / FUNCTION AND ITS CURRENT LATENCYREQUESTS PER SECOND / DATA VOLUMELANGUAGE, FRAMEWORK, WHERE IT RUNS

Your prompt

Analyze this performance data and find the actual bottleneck.

Profiler output or timings:
[PASTE FLAMEGRAPH SUMMARY, pprof TOP, OR ENDPOINT TIMINGS]
What is slow: [ENDPOINT / JOB / FUNCTION AND ITS CURRENT LATENCY]
Expected load: [REQUESTS PER SECOND / DATA VOLUME]
Stack: [LANGUAGE, FRAMEWORK, WHERE IT RUNS]

Deliver:
1. Your read of the data: where time is really going (distinguish CPU-bound, I/O-wait, lock contention, GC, and N+1-style repetition).
2. The top 3 fixes ranked by expected impact vs effort, each with the specific code region to change.
3. One thing people usually misdiagnose in this kind of profile and why it is probably not the problem here.
4. How to confirm the fix worked: what metric, measured how.

Do not suggest caching or "use a faster language" until you have shown the data supports it.

Paste it into Muse or any assistant. Blank fields stay as [brackets].

More like this

ADR Writer

Security Audit

Merge Conflict Resolver

Repo Onboarding Tour

Commit Message Writer

Error Decoder