perf-review

A performance audit analyzes code changes by profiling query plans, resource usage, and caching strategies to identify hotspots and scalability concerns. It requires access to the repository, profiling data, and benchmarks to map hot paths and evaluate load impact.

Deep performance profiling evaluates query plans, index coverage, and caching layers beyond standard code review checks. You need it when reviewing feature branches or subsystems to identify performance bottlenecks, map hot paths, and estimate load impact before deployment.

Checking for resource exhaustion involves mapping hot paths across the codebase and analyzing data flows to evaluate efficiency and scalability. The audit produces a structured performance report identifying hotspots and resource limits suitable for follow-up engineering sprints.

Analyzing caching strategies and query plans requires access to the repository, profiling data, and benchmarks. Without these inputs, the multi-step workflow from hot-path mapping to adversarial review cannot accurately evaluate index coverage or estimate load impact.

The best way to identify performance bottlenecks is running a dedicated performance audit that profiles query plans and evaluates caching layers. This maps hot paths across the codebase to pinpoint where bottlenecks originate and produces a structured optimization report.

Performance review is limited by its dependence on existing profiling data and benchmarks, meaning it cannot accurately estimate load impact or map hot paths without repository access. It focuses on hotspots and caching strategies rather than standard code review checks.