Unlock PostgreSQL’s True Performance with Local SSDs
summary
Claims that local NVMe SSDs beat remote storage by large margins with concrete benchmarks: PGbench/TPCB shows ~6x faster throughput, TPCC reports 8.5x and TPC-H analytic runs ~8x faster on identical CPU/memory; real customers see ~3x production gains after migrating to Ubloud’s managed Postgres (Postgres 17) using local NVMe. Ubloud is open source, uses full-standby cutovers for scaling/maintenance, and notes NVMe can deliver 2.5M IOPS on inexpensive drives (example $600) while reducing cloud remote-storage monthly costs.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:13Local vs remote storage
- 9:49Why remote storage dominates
- 15:57Evolution of storage tech
- 22:01Local SSDs as default
- 26:16Remote storage advantages
- 30:56Q&A session
related talks
27mPostgres isn’t slow, your storage is
28mRun PostgreSQL in Warp Speed Using NVMe/TCP in the Cloud
36mBest Practices in PostgreSQL Tuning: Navigating Key Performance Bottlenecks in the Cloud
50mPostgres vs. Linux filesystems
43mPostgreSQL in the cloud: Theory and Practice
42mPostgreSQL Distributed: Architectures & Best practices
26mTop 10 reasons to choose Flexible Server for Azure Database for PostgreSQL
54mPostgres: From Cloud to Hybrid and On Prem Again