The same API: 600 requests a second, 200 threads, 20 database connections. At 10 seconds orders v2 ships: the order page now shows the order's 10 line items. No traffic spike, no slow query in the logs, nothing obviously wrong in review.
From 15 to 70 seconds, answer at least 580 requests a second before clients give up, with a p99 of 300 ms or less.
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
1,000/s
Press Start
00:0001:00
Answered in time–
Too late–
Rejected or failed–
Latency (answered in time)
500 ms
Press Start
00:0001:00
p50–
p95–
p99–
Requests waiting for a thread
200
Press Start
00:0001:00
Queued–
Saturation
100%
Press Start
00:0001:00
Threads busy–
Connections in use–
Database CPU–
Memory
1,536 MB
Press Start
00:0001:00
Used–
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.