Profile application performance, identify bottlenecks, and optimize hot paths using CPU profiling, flame graphs, and benchmarking. Use when investigating performance issues or optimizing critical code paths.

Profiling & Optimization Table of Contents [Overview]( overview) [When to Use]( when to use) [Quick Start]( quick start) [Reference Guides]( reference guides) [Best Practices]( best practices) Overview Profile code execution to identify performance bottlenecks and optimize critical paths using data driven approaches. When to Use Performance optimization Identifying CPU bottlenecks Optimizing hot paths Investigating slow requests Reducing latency Improving throughput Quick Start Minimal working example: Reference Guides Detailed implementations in the references/ directory: Guide Contents [Node.js Profiling](references/nodejs profiling.md) Node.js Profiling [Chrome DevTools CPU Profile](references/chrome devtools cpu profile.md) Chrome DevTools CPU Profile [Python cProfile](references/python cprofile.md) Python cProfile [Benchmarking](references/benchmarking.md) Benchmarking [Database Query Profiling](references/database query profiling.md) Database Query Profiling [Flame Graph Generation](references/flame graph generation.md) Flame Graph Generation Best Practices ✅ DO Profile before optimizing Focus on hot paths Measure impact of changes Use production like data Consider memory vs speed tradeoffs Document optimization rationale ❌ DON'T Optimize without profiling Ignore readability for minor gains Skip benchmarking Optimize cold paths Make changes without measurement

profiling-optimization