An API pod and a nightly report job share a 4-core node. The API needs 2.5 cores at peak. Neither has CPU requests or limits. At 10 seconds the report job starts and uses every core it can get.
From 10 to 60 seconds, answer at least 99% of requests with p99 at or under 150 ms.
ready00:00 / 01:00Success · 10 s–p99 · 10 s–
Goal · measured 00:10–01:00
0 changes · par 1
Requests answered ≥ 99.0%not measured yet
p99 latency ≤ 150 msnot measured yet
Service map
Shared node · pausedSelect a component to inspect
SYSTEM BOUNDARYsame nodeUsers500 req/sCLIENTAPI podgets 2.5 of 2.5 cores neededSERVICEReport jobidleCACHE
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
Shared node · pausedSelect a component to inspect
SYSTEM BOUNDARYsame nodeUsers500 req/sCLIENTAPI podgets 2.5 of 2.5 cores neededSERVICEReport jobidleCACHE
SYSTEM BOUNDARYsame nodeUsers500 req/sCLIENTAPI podgets 2.5 of 2.5 cores neededSERVICEReport jobidleCACHE
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.