S3-based databases cache in memory and NVMe, making disk vs S3 latency gap smaller than expected
mgill25 · x · 2026-11-04
Pekka Enberg explains why S3-based database architectures stay competitive: reads are amortized via memory and local NVMe caching, so read performance roughly matches local-disk setups with only heavier tail latency, while writes already require a network round trip for replication—making the S3 penalty smaller than commonly assumed, especially with S3 Express.
More from Infra
- Sam Altman? No—Bezos Calls for Nuclear-Powered Offshore Data Center Platforms — beffjezos · 2026-11-04
- NEURA launches Neuron AI, but Europe's Physical AI test is whether the stack matures together — ingliguori · 2026-11-04
- gpu-unlock project claims up to 2x FP16 tensor throughput for RTX 20/30/40 cards — paranoidray · 2026-11-04
- These 10 GPU optimization papers are why your model runs fast today — NandoDF · 2026-11-04
- One prompt to audit cross-region traffic: dev cut trans-Atlantic latency by moving a service — DanielLockyer · 2026-11-04
- SurrealDB 4 launches as multi-model ACID database for the agentic era — Scobleizer · 2026-11-04