performance-reviewer

To detect N+1 queries and memory growth, you can trace how code behaves under real data and load to identify scaling bottlenecks. This process requires evidence like query counts and memory usage to quantify impact.

Reviewing code for latency and throughput issues involves quantifying these metrics across critical paths under realistic workloads. It guides targeted analysis by requiring concrete evidence such as external call counts and latency measurements.

Identifying performance regressions in data-heavy loops and I/O-bound paths requires tracing code behavior under production scale. You evaluate impact using constraints like memory usage and throughput to guide improvements.

Yes, performance code review for large result sets provides actionable recommendations and guardrails. It documents findings with concrete scale metrics and traceable evidence to support optimization efforts and prevent regressions.

To quantify performance costs in a production deployment, you need evidence such as query counts, latency, memory usage, and external calls. These constraints evaluate impact and guide targeted improvements.