The shop's backend can serve 950 requests a second. Normal traffic is 500; 80% of it is people viewing the product page. At 10 seconds the sale opens and traffic jumps to 5,000 a second.
From 10 to 90 seconds, serve at least 99% of shoppers, with no one waiting more than a minute, without adding backend instances.
ready00:00 / 01:30Success · 10 s–p99 · 10 s–
Goal · measured 00:10–01:30
0 changes · par 2
Shoppers served ≥ 99.0%not measured yet
Longest wait (s) ≤ 60 snot measured yet
Backend instances ≤ 1×not measured yet
Service map
Flash sale · pausedSelect a component to inspect
SYSTEM BOUNDARY500/sShoppers500 req/sCLIENTCDN / edgepass-throughSERVICEShop backend500/s of 950/sSERVICE
All components healthy.requestretrytrial call (half-open)failed
What changed
Turn on a fault or change a defence while the run plays. Its effect shows here: the 5 seconds before against 5 seconds after it settles.
Service map
Flash sale · pausedSelect a component to inspect
SYSTEM BOUNDARY500/sShoppers500 req/sCLIENTCDN / edgepass-throughSERVICEShop backend500/s of 950/sSERVICE
SYSTEM BOUNDARY500/sShoppers500 req/sCLIENTCDN / edgepass-throughSERVICEShop backend500/s of 950/sSERVICE
All components healthy.requestretrytrial call (half-open)failed
What changed
Turn on a fault or change a defence while the run plays. Its effect shows here: the 5 seconds before against 5 seconds after it settles.
Dashboard
Requests per second
100/s
Press Start
00:0001:00
Answered–
Failed–
Latency
100 ms
Press Start
00:0001:00
p50–
p95–
p99–
Events and logs
Nothing yet. Faults, timeouts, retries, breaker changes, shedding, cache expiry and your own changes appear here, and as markers on the charts.
Slowest recent request
Press Start to see requests.
This is a simulation. Its numbers come from a model of a typical system, not from measuring real servers. The same link and seed always give the same run. How the Chaos Lab works.