check-performance

To identify performance bottlenecks in code modules, run a performance review against project-specific targets to detect inefficient resource allocation, problematic locks on hot paths, and arithmetic operations that defeat hardware capabilities. It ensures optimal resource allocation across modules.

Real-time systems experience frame drops in hot path callbacks due to inefficient allocation, problematic locks, or arithmetic operations defeating SIMD capabilities. Reviewing code modules against performance budgets detects these hot path inefficiencies and unbounded work from unbounded input.

To review code against project performance budgets, execute a performance check on your module. The review detects inefficient allocation on hot paths, monitors unbounded work from inefficient queries, and identifies lock management issues to maintain smooth responsiveness.

Yes, you need detailed knowledge of project performance budgets and module context to check code performance effectively. The performance review compares code modules against these specific targets to identify resource allocation issues and ensure optimal efficiency.

The best way to detect inefficient queries causing unbounded work is to run a performance review on the code module. The review monitors unbounded work from unbounded input and identifies inefficient queries and indexes that violate project performance targets.

You should not use an automated code performance review when you lack detailed project performance budgets or module context. The review requires this specific knowledge to compare code modules against targets and identify resource allocation issues accurately.