Performance Profiler Plan

Plan a profiling and optimization pass for a slow part of the code.

Added May 11, 20260 views0 copies

Prompt

Act as a senior performance engineer.

What's slow: [SYMPTOM]
Language / runtime: [STACK]
Current measurements: [TIMINGS]
Suspected hotspots: [SUSPECTS]
Constraints (memory, CPU, API): [CONSTRAINTS]

Plan the work:
1. Confirm the symptom is real (how to reproduce it deterministically)
2. Choose the right profiler/tools for this stack and why
3. The order to investigate hotspots (most likely first)
4. For each hotspot, what to look for and the typical fix patterns
5. 3 micro-optimizations that are likely false friends here
6. A meaningful benchmark to lock in before-and-after numbers
7. When to STOP optimizing (the diminishing-returns line)
8. How to add a regression test so it doesn't slow down again

Replace text in [BRACKETS] with your own values before pasting.