News for hackers. Stuff that matters.
Re:Cache made consistent: Meta’s cache invalidation solution by uvdn7 on Wednesday June 08, 2022 @06:07PM (#31675000)
> De facto, it is a cache server, with the associated performance decrease. Isn't the main purpose of caching to improve performance?

Polaris only receives cache invalidation event, and doesn't serve any client queries.

> so then, to synchronize among the service instances

It doesn't synchronize among the service instances. It's actually basically stateless. It pretends to be a cache server only for receiving invalidation events, and acts as a client, and assumes no knowledge of the cache internals.

Re:Cache made consistent: Meta’s cache invalidation solution by pdevr on Wednesday June 08, 2022 @06:25PM (#31675194)
Thanks for the clarification. However, in that case, won't the querying of all the cache copies/replicas turn out to be the bottleneck at high volumes? Because you are going to have to check all the existing copies/replicas somewhere, right?
Re:Cache made consistent: Meta’s cache invalidation solution by uvdn7 on Wednesday June 08, 2022 @06:27PM (#31675211)
Yep. Polaris checks can be sampled, but still covers pretty much all types of workload and scenarios/races over time.