perf-profile

A performance bottleneck analysis reviews API handlers, middleware, database access, and hot code paths to locate slowdowns. It compares current behavior against latency and memory budgets to produce prioritized optimization recommendations with estimated impact.

The best way to prioritize code optimization fixes is by ranking identified bottlenecks against performance budgets. This generates a prioritized list of quick wins and areas requiring runtime profiling, estimating the impact of each fix before you begin work.

Profiling API latency and database queries requires a full-system or single-system evaluation that inspects I/O paths and middleware. It compares current response times against established throughput and latency budgets to find expensive queries and slowdowns.

Yes, read-only static inspection can find memory usage bottlenecks by reviewing memory growth patterns and I/O paths. This approach locates likely slowdowns without executing code, comparing current behavior against memory budgets to guide optimization.

Yes, this performance profiling approach works for game frame-time analysis by applying budget-based evaluation to game codebases. It identifies hot code paths and evaluates frame-time against target budgets to produce prioritized optimization recommendations.

You need runtime profiling after a static performance review when a suspected bottleneck requires dynamic execution data to confirm. The review explicitly flags these areas, separating confirmed quick wins from subsystems needing deeper runtime analysis before action.