“When adding jitter to scheduled work, we do not select the jitter on each host randomly. Instead, we use a consistent method that produces the same number every time on the same host. This way, if there is a service being overloaded, or a race condition, it happens the same way in a pattern. We humans are good at identifying patterns, and we're more likely to determine the root cause”
https://builder.aws.com/content/3EumjoZascWd1oZiEgL8ORlv3qE/timeouts-retries-and-backoff-with-jitter
Tomasz Nurkiewicz
npub1g4…32ll5
2026-08-12 15:50:12 UTC
Author Public Key
npub1g4g5mdxgxmvz0qhrfqgcq9skl4htxkty2ydv4zv3lllgdpsnap4qh32ll5Seen on
wss://relay.ditto.pubPublished at
2026-08-12 15:50:12 UTCEvent JSON
{
"id": "54add06e31a127393329199e18304bc00a06fc95d9049a72a8215d1247b769d1",
"pubkey": "45514db4c836d82782e34811801616fd6eb35964511aca8991fffe868613e86a",
"created_at": 1786549812,
"kind": 1,
"tags": [
[
"proxy",
"https://fosstodon.org/users/nurkiewicz/statuses/117083328544232978",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.ditto.pub"
]
],
"content": "“When adding jitter to scheduled work, we do not select the jitter on each host randomly. Instead, we use a consistent method that produces the same number every time on the same host. This way, if there is a service being overloaded, or a race condition, it happens the same way in a pattern. We humans are good at identifying patterns, and we're more likely to determine the root cause” \n\nhttps://builder.aws.com/content/3EumjoZascWd1oZiEgL8ORlv3qE/timeouts-retries-and-backoff-with-jitter",
"sig": "014cb71b72d7cc602029eda23fa961d1d9938381b022356cc7c9e6f5eda335a75f3707ff4994cbd493bb81344a7895af98cb8c86fe2cff0e7e2ae38e1653aba5"
}