What is the bottleneck?
Practice this questionDiscussion template: use your own project facts, ownership, and measured outcomes. Bracketed text is a placeholder.
Short explanation:
A bottleneck is the resource or serialized step that limits throughput or increases waiting time. It can move after an optimization, so it is a property of a workload and system state rather than a permanent label on a component. Traces and saturation measurements help identify it.
Key points:
-
It is the component limiting throughput or increasing latency.
-
I would identify it from traces and resource metrics, not guess from the architecture.
-
Compare time spent executing with time spent waiting; a busy CPU and a long connection queue need different responses.
Interview point:
- Explain how the evidence identifies the limiting stage before choosing a fix.
Adapted from 10_RESUME_PROJECT_DEEP_DIVE.md · “What is the bottleneck?”. Code examples are study fragments. Difficulty and core labels are editorial estimates; version-specific behavior should be checked against your project.