Software & DevOpsDone with Cursor Dec 1, 2025
Troubleshoot a production-only performance issue
A developer used Cursor and Warp agents to analyze NestJS database queries and recommend indexes for a production performance problem.
- What They Did
- A page was slow in production but not in the dev environment. The developer asked a Cursor/Warp agent to list possible causes and the steps to fix them. The agent read the codebase, worked out which database queries NestJS was making, and said which database indexes should be used.
- How It Went
- After the developer added the recommended indexes, page load performance improved significantly. The source gives no timings or figures.
- Worth Knowing
- The agent worked from the codebase and produced a list of candidate causes, so the developer still had to apply the indexes and check the result in production.
Try it yourself with Cursor
Our [framework, e.g. NestJS] app is slow in production but not locally, specifically [endpoint or page]. Read the code and database queries involved, identify the slowest or most repeated ones, and recommend indexes or query changes with an explanation of why. You're done when you have a ranked list of fixes with the exact migration or code change for each. Don't run anything against the production database; show me the changes first.