---
title: "Comment by Abhinav Sharma on \"System Design Drill Day 2: Caching, TTLs and Cache Stampedes\" | Hashnode"
description: "The jitter point deserves more attention than it gets. If every key gets the same TTL, they were all written in the same deploy and will expire together, so the"
url: "https://hashnode.com/posts/system-design-drill-day-2-caching-ttls-and-cache-stampedes/6ad732771e0bcca489a2809b/comment/6ad73c3752650cb3517d0510"
---

[Discussion](https://hashnode.com/posts/system-design-drill-day-2-caching-ttls-and-cache-stampedes/6ad732771e0bcca489a2809b)

Comment [System Design Drill Day 2: Caching, TTLs and Cache Stampedes](https://hashnode.com/posts/system-design-drill-day-2-caching-ttls-and-cache-stampedes/6ad732771e0bcca489a2809b)

[Abhinav Sharma](https://hashnode.com/@abhinavs1920)

[Oct 20](https://hashnode.com/posts/system-design-drill-day-2-caching-ttls-and-cache-stampedes/6ad732771e0bcca489a2809b/comment/6ad73c3752650cb3517d0510)

The jitter point deserves more attention than it gets. If every key gets the same TTL, they were all written in the same deploy and will expire together, so the herd reforms on a schedule. Even 10 percent randomness spreads the misses out enough to matter.

[Anish Ansari](https://hashnode.com/@anish78)

[Oct 20](https://hashnode.com/posts/system-design-drill-day-2-caching-ttls-and-cache-stampedes/6ad732771e0bcca489a2809b/comment/6ad73c3752650cb3517d0510#reply-6ad76a34dfa8da14174a8239)

Thanks Abhinav, keys written in the same deploy expiring together is exactly how it bites in practice. A little jitter turns one big stampede into a trickle the database can handle.