Performance Regression Detective
Find which change slowed something down.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Help me find which change made something slower. What is slower and by how much (include the measurements): [REGRESSION_DESCRIPTION]. Environment and how I measured: [ENVIRONMENT_AND_METHOD]. Recent changes (commits, releases, dependency updates, configuration, data growth): [RECENT_CHANGES]. Tools available (profiler, tracing, logs, git bisect): [TOOLS]. Walk through the tree: 1. Is the regression real? Repeat measurements, control for noise (cache, load, time of day), and write a repeatable benchmark that I can run on any commit. 2. Is it code or environment? Compare the same code on the old and new environment, or old code on the new environment. 3. Is it data? Check growth in data size, new data shapes, and missing indexes. 4. Bisect: use git bisect with the benchmark as the test; give the exact commands and the criterion for good and bad. 5. Profile the slow version and the fast version side by side; compare flame graphs or call counts to see where time shifted. 6. Check the usual suspects: new queries inside loops, removed caching, increased logging, serialization changes, dependency upgrades, configuration defaults, and lock contention. Deliver an investigation plan with commands for my tools, the benchmark script outline, how to interpret the profile, and a fix and prevention plan (performance test in continuous integration with a threshold). State assumptions.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.