News for hackers. Stuff that matters.
Re:Staying Out of TTL Hell by hinkley on Wednesday March 10, 2021 @01:16PM (#26414214)
As the TTL shrinks to a smaller multiple of the time needed to generate the response, this problem becomes magnified.

A two second response with a 10 second TTL could see 20% of the queries all trying to refresh the same cache at once. With a single server you can use promise caching to dedupe such things, with a cluster that's more difficult to avoid.

Background processes are good for spiky traffic, and with reddit and HN around some of us at least have been trained that some information on a page is purely advisory. Do I have 22 upvotes or 28? Give it a couple minutes and try again.

But what that work does is make you look at what the cost is of certain information, and some people are not comfortable with that. With caching you can delude yourself that you're getting a bargain on all of this information overload, even though the worst case scenarios and statistical clumping say you're off your gourd.

There are no comments on this comment yet.