Checkout runs on identical instances that can each handle 500 requests a second at 100% CPU. Normal traffic is 900 a second; at 20 seconds a sale doubles it to 1,800. You have 3 instances.
From 20 to 60 seconds, answer at least 99.5% of checkouts with p99 at or under 150 ms, using no more than 5 instances.
ready00:00 / 01:00Success · 10 s–p99 · 10 s–
Goal · measured 00:20–01:00
0 changes · par 1
Checkouts answered ≥ 99.5%not measured yet
p99 latency ≤ 150 msnot measured yet
Instances ≤ 5not measured yet
Service map
Checkout fleet · pausedSelect a component to inspect
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–
Utilisation
100%
Press Start
00:0001:00
Busy–
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.