A search fans out to 20 index shards and waits for all of them. Each shard answers in about 8 ms, but from 5 seconds on, each one pauses for 400 ms about 1% of the time (garbage collection, compaction).
From 5 to 60 seconds, keep p99 search latency at or under 100 ms and answer at least 99% of searches.
ready00:00 / 01:00Success · 10 s–p99 · 10 s–
Goal · measured 00:05–01:00
0 changes · par 1
p99 search latency ≤ 100 msnot measured yet
Searches answered ≥ 99.0%not measured yet
Service map
Search fan-out · pausedSelect a component to inspect
SYSTEM BOUNDARY300/s×20Users300 searches/sCLIENTSearch APIwaits for all 20SERVICEIndex shards20 shards × 3 · p50 8 msDATA 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
Search fan-out · pausedSelect a component to inspect
SYSTEM BOUNDARY300/s×20Users300 searches/sCLIENTSearch APIwaits for all 20SERVICEIndex shards20 shards × 3 · p50 8 msDATA STORE
SYSTEM BOUNDARY300/s×20Users300 searches/sCLIENTSearch APIwaits for all 20SERVICEIndex shards20 shards × 3 · p50 8 msDATA 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–
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.