performance-profiling

Use when code is slow, latency has regressed, or throughput has dropped and you need measurements before fixing it. USE FOR: profiling a hot path in a service, comparing baseline vs optimized runtime, finding CPU or memory bottlenecks, investigating slow database or I/O paths, and verifying a performance regression fix. DO NOT USE FOR: guessing at optimizations without data or using this only for feature prioritization.