domains / families / software-engineering / cs-performance-profiler

cs-performance-profiler

separate

Performance Profiler

When to use

• App is slow and you don't know where the bottleneck is
• P99 latency exceeds SLA before a release
• Memory usage grows over time (suspected leak)
• Bundle size increased after adding dependencies
• Preparing for a traffic spike (load test before launch)
• Database queries taking >100ms

When not to use

• Optimizing without measuring
• Testing in development
• Ignoring P99
• Premature optimization
• Not re-measuring
• Load testing production

Skill page

Source