Comment

Comment by chonghaoju

At ~35TB Postgres we ended up separating pg_wal onto its own volume first — write amplification there was quietly eating 20–30% of our NVMe throughput before we caught it.
parent chonghaoju 2 months ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton