A Java recommendations service with a 1 GB heap answers 500 requests a second. At 10 seconds v3.2 ships, adding a per-session cache. Watch the live heap after each GC, the time spent in GC, and what happens when there is no room left.
From 10 seconds to 3 minutes, answer at least 99.5% of requests with a p99 of 150 ms or less.
SYSTEM BOUNDARY500/scache: unboundedUsers500 req/sCLIENTRecommendations300 MB live / 1 GBSERVICEDatabaserecommendationsDATA 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
JVM heap · pausedSelect a component to inspect
SYSTEM BOUNDARY500/scache: unboundedUsers500 req/sCLIENTRecommendations300 MB live / 1 GBSERVICEDatabaserecommendationsDATA STORE
SYSTEM BOUNDARY500/scache: unboundedUsers500 req/sCLIENTRecommendations300 MB live / 1 GBSERVICEDatabaserecommendationsDATA 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
Heap
2,000 MB
Press Start
00:0001:00
Live after GC–
In use–
Time in GC
100%
Press Start
00:0001:00
GC–
Requests per second
500/s
Press Start
00:0001:00
Answered–
Failed–
Latency
100 ms
Press Start
00:0001:00
p50–
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.