performance-review

To find performance bottlenecks in a pull request, analyze the code change using a phase-based approach to surface N+1 queries and provide concrete evidence like estimated complexity. This yields a prioritized optimization plan with before/after examples.

The best way to review code for algorithmic efficiency and memory leaks is applying a three-bucket framework covering algorithms, IO/query efficiency, and memory management. This surfaces hot-path issues and delivers actionable refactoring recommendations.

Yes, you can use this performance review to analyze code scalability under heavy load. It applies context research and comparative analysis to surface high-impact performance findings at scale, including hot data considerations and resource impact.

To get actionable recommendations for inefficient algorithms, run a phase-driven analysis that assesses issues and estimates resource impact. You receive precise before/after code examples and a prioritized optimization plan to guide changes.

You should not use static code review for performance optimization when you need real-time runtime profiling data rather than estimated complexity. This approach analyzes code changes to identify bottlenecks but does not execute live load testing.

Your code change introduces performance bottlenecks due to inefficient algorithms, IO query inefficiencies, or poor memory management. A phase-based analysis identifies these issues by evaluating hot-path execution and estimating the real-world resource impact.