Removing bottlenecks in order
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
apply fixes in order of impact, one at a time.
Planned topics
- Find the bottleneck from evidence: profiler flame graphs, database query statistics, thread and pool metrics, resource saturation (USE: utilization, saturation, errors).
- Fix the largest one, re-measure; the next bottleneck then shows.
- Typical order: remove unnecessary work (N+1 queries, missing index), then caching, concurrency, and only then micro-tuning.
- Amdahl's law: removing a part that is 5% of the time can at best gain 5%.
Draft outline details
Demonstration
Table of the checkout path: step | share of p99 | change | new share. Example: 45% in a query with a missing index, fixed first.
Check your understanding
Why not optimize a step that takes 3% of time?
Show answer
Even eliminating it gains at most 3%.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.