PWA · Interviews · pwa-interview under load on an 8-core 16GB box — full benchmark scripts included

I see point 3 differently. The trade-off depends on your read/write ratio: read-heavy with little writing means caching actually widens the inconsistency window.

This matches what we see in production. We only hit it past 3k QPS; the earlier load tests showed nothing — the test traffic was too clean, with no long-tail requests.

Has anyone run a controlled experiment? I did, reducing it to a single variable, and the difference was 4% — within noise. So I suspect the main cause is something else.

We have run this in production for two years without hitting it. That said, we never reached this scale, so our experience is not really evidence here.

I just read the pwa-interview source — the author actually explains the reasoning in a comment, roughly "so that it degrades into predictable behaviour in extreme cases".

Worth learning from this debugging approach. We went straight at the logs and took a much longer route.