←back to thread

High-performance read-through cache for object storage

(github.com)
65 points pranay01 | 1 comments | 20 Sep 25 04:13 UTC | HN request time: 0s | source
Show context
onethumb ◴[20 Sep 25 07:07 UTC] No.45311154[source]▶
This looks super interesting for single-AZ systems (which are useful, and have their place).

But I can't find anything to support the use case for highly available (multi-AZ), scalable, production infrastructure. Specifically, a unified and consistent cache across geos (AZs in the AWS case, since this seems to be targeted at S3).

Without it, you're increasing costs somewhere in your organization - cross-AZ networking costs, increased cache sizes in each AZ to be available, increased compute and cache coherency costs across AZs to ensure the caches are always in sync, etc etc.

Any insight from the authors on how they handle these issue on their production systems at scale?

replies(2): >>45311421 #>>45311444 #
1. trueismywork ◴[20 Sep 25 08:12 UTC] No.45311444[source]▶
Not the author but. Its a user side read through cache, so no need for pre-emptive cache coherence as such. But there will be a performance penalty for fetching data under write contention irrespective of whether you have single az/multiple AZ. The only way to mitigate the performance penalty here is to have accurate predictive fetching which works for usage patterns.