perf-profile

To profile CPU and memory bottlenecks, apply a profiling workflow to targeted systems or full-stack scenarios. It analyzes your codebase to surface per-frame hotspots, memory growth, and rendering overhead, returning a structured report with impact estimates and prioritized optimization steps.

Identifying rendering bottlenecks requires measuring against predefined performance budgets for frame time and draw calls. The profiling process analyzes rendering overhead across your codebase, returning a structured report that highlights hotspots and budget overruns with prioritized optimization recommendations.

Yes, you can profile performance against custom budgets by reading targets for frame time, memory, load times, and draw calls from design docs or configuration files. The profiling workflow measures actual system performance against these budgets to identify overruns.

To start profiling targeted systems, you need established performance budgets, specific profiling targets, and reproducible workflows. Providing a system name or specifying a full deployment allows the profiling process to generate a comprehensive performance report with hotspots and impact estimates.

The best way to prioritize performance optimization is to run a comprehensive profiling workflow across the full-stack deployment. It generates a structured report containing hotspots, impact estimates, and prioritized optimization steps based on measured CPU, memory, and rendering bottlenecks.