The dashboard requests stock counts from 20 warehouses at once. It can show the report once every reply arrives.
One stock report
Model time
19 replies at 40 ms1 reply at 800 ms
0 ms200 ms deadline800 ms
Final replyWarehouse 20
Due at 800 ms
Stock reportWaiting for replies
0 of 20 warehouses have replied
In this example, each warehouse replies in 40 or 800 milliseconds. The report is due by 200 ms. The timings are invented.
Set up the report
Chance the complete stock report is late
%
About 18.2 in 100 complete reports would miss the 200 ms deadline.
One report needs a reply from every warehouse. Any reply arriving after 200 ms makes the whole report late.
Why this number?
Every reply has to be fast.
An all-fast report needs every independent call to finish quickly. One slow reply is enough to hold it up.
81.8%Every reply fast18.2%At least one slow
Probabilities in this model, not counts from a sampled workload.
One warehouse request1%
Complete report · 20 replies18.2%
Same scale: 0–100%. Change the warehouse count to compare.
Each warehouse still has a 1% chance of a slow reply. Checking 20 warehouses gives a report 20 chances to encounter a slow reply; one is enough to hold up the whole report.
Each call: 1.0% slow40 ms when fast · 800 ms when slow
Change each call’s slow chance
These are authored probabilities for this model. No service is being measured.
One selected possible report
Will the stock report be ready?
model ms
Select a warehouse to follow its reply. On the board, use Left/Right or Home/End.
Warehouse 20
A bar groups reports with the same number of slow replies. Its height shows the model probability.
Select a count on the plot. Left/Right chooses the next possible count; Home/End goes to the first/last. The selector below works too.
Launch40 ms · fast200 ms · deadline800 ms
Playback runs at half speed. The clock shows model time.
All calls start together. Move the clock to see the gate work.
Same calls, different company
The per-call number doesn’t settle the report.
Knowing each call’s slow chance leaves a range of possible report risks. The way the replies coincide matters.
Same per-call chances allow1–20%of reports to miss the deadline
WHERE YOU CAN USE THIS
Measure the wait the person experiences.
The stock dashboard is one example of a job that needs several parallel results: a search page merging indexes, a dashboard reading several services, or an agent waiting for every required check. A quick individual call does not guarantee a quick complete result.
Two design questions follow. Does the person need every reply before they can continue? Do delays share a cause, such as an overloaded dependency? This bench changes the second question while keeping every reply required. Showing partial results, setting timeouts or changing that completion rule needs a different calculation.