Three in ten requests are checkouts, and each one calls an external payments provider. At 15 seconds, the provider starts taking about four seconds to answer.
You cannot fix the provider. Keep product pages fast and available while it is slow. Checkouts may fail; the rest of the site must not.
SYSTEM BOUNDARY0 req/sno timeout · no retriespool 0/30Users0 req/sCLIENTAPI0/120 threadsSERVICEPayments0 calls/sTHIRD PARTYPostgres8 ms/queryDATA STORERedishit rate 92%CACHE
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
Succeeded–
Failed–
Latency
1.0 s
Press Start
00:0001:00
p50–
p95–
p99–
Saturation
100%
Press Start
00:0001:00
API threads–
DB pool–
Postgres CPU–
Payments calls per second
500/s
Press Start
00:0001:00
Calls–
Failing–
Cache hit rate
100%
Press Start
00:0001:00
Hit rate–
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.