Playground/ Engineering & Systems/ System Bottleneck Explorer
⚙️ Engineering & Systems

System Bottleneck Explorer

Set a throughput for each pipeline stage. See which one caps the whole system.

URL Collector 180 / min
File Fetcher 60 / min
Data Extractor 120 / min
Validation 150 / min
Storage 90 / min
Analytics 200 / min
System Throughput
–
Bottleneck Stage–
Time to process 10,000 items–

A simplified model: treats each stage as a straight-line throughput with no queuing, retries or parallelism, to isolate the bottleneck idea.

What is happening?

A pipeline can only move as fast as its slowest stage: the system throughput is the minimum of the six stage throughputs, not their average. Speeding up a stage that isn't the bottleneck changes nothing; the whole point of finding the bottleneck first is that it's the only place extra capacity actually helps.

Under the Hood
Six stage throughputs (items/min) ↓ System throughput = min(all six) ↓ Bottleneck stage highlighted, batch time estimated

Inputs

  • Six adjustable throughput sliders

Processing

  • Min-of-stages bottleneck rule

Output

  • System throughput
  • Bottleneck stage
  • Time estimate

Technology

  • Vanilla JavaScript

Explore another experiment

More Playground experiments are on the way.