Simulation run on this device. Scenario values are not sent anywhere — the engine is fully local.
system design simulation · free
Retry & Jitter Studio
Measure retry amplification, then spread it back out with backoff and jitter.
What do three retries really do to the dependency's load?
Engine 1.0.0 · simulation
10 %
3
100 ms
0 %
Spread retries randomly inside ±this band to avoid synchronized herds.
×1.11load multiplier on the dependency
- Expected attempts / call
- 1.111
- Expected retry delay added
- 12 ms
- Retry 1 window
- 100–100 ms
- Retry 2 window
- 200–200 ms
- Retry 3 window
- 400–400 ms
Without jitter, every failed client retries at the same instant — the herd lands together.
Method
- Expected attempts per call follow the geometric series Σpⁱ for i = 0…retries.
- Retry windows are exponential backoff centers spread by ±jitter; zero jitter means synchronized herds.
- Amplification shown is per-call site — multiply again per hop for cascades.