Order history pages hit one PostgreSQL primary with 8 cores, 800 page views a second. At 10 seconds v8 ships "recent orders": one more query per page.
From 15 to 60 seconds, answer at least 99.5% of pages with p99 at or under 200 ms, without spending more on the database (cost 1×).
ready00:00 / 01:00Success · 10 s–p99 · 10 s–
Goal · measured 00:15–01:00
0 changes · par 1
Pages answered ≥ 99.5%not measured yet
p99 latency ≤ 200 msnot measured yet
Database cost ≤ 1× costnot measured yet
Service map
Orders database · pausedSelect a component to inspect
SYSTEM BOUNDARYIndex ScanUsers800 page views/sCLIENTApp servers6 app servers · 20% CPUSERVICEPostgreSQL8 cores · 2 ms/queryDATA STORE
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
Orders database · pausedSelect a component to inspect
SYSTEM BOUNDARYIndex ScanUsers800 page views/sCLIENTApp servers6 app servers · 20% CPUSERVICEPostgreSQL8 cores · 2 ms/queryDATA STORE
SYSTEM BOUNDARYIndex ScanUsers800 page views/sCLIENTApp servers6 app servers · 20% CPUSERVICEPostgreSQL8 cores · 2 ms/queryDATA STORE
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–
Database CPU
100%
Press Start
00:0001:00
CPU–
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.