[djhworld]

I played a really small role when looking at some caching data for a system another team run (their logs are ingested and processed by us) and noticed that a lot of the time the content requested is only requested once - this is sometimes referred to as a "one hit wonder"

Once I told them this and showed them some graphs etc they did an experiment to set it to only cache on the 2nd hit, and this reduced the write rate on the disks massively - potentially increasing their lifespan quite significantly (saving money)

They did the hardwork of engineering it, experimenting etc but I'm proud that my little contribution helped drive a real change in a domain outside my team :)

[quickthrower2]

One hit wonder - thanks I’ll introduce this concept to my boss and see if it helps us: we accidentally lost some caching due to a bug but there was no measured performance penalty on our production performance tests. Hence we didn’t notice until someone looked at the code. Could be a one hit wonder! It’s a nice concept to think about in any caching code.