ClickHouse explains why Postgres shared_buffers gets costlier as connections rise
arpit_bhayani · x · 2026-07-27
A reference to a ClickHouse blog explains why Postgres sharedbuffers gets more expensive as connection count rises:
- Each backend process maps the shared buffer segment through its own page tables.
- Linux/OS memory is managed in 4 KB pages, so more connections mean more page-table entries and more overhead.
- The post points readers to the ClickHouse write-up for the deeper explanation.
Related event: Why Postgres Shared Buffers Get Pricier with More Connections(2 posts)→
More from Infra
- Dedicated Hardware for Running AI Agents at Scale Arrives — cyrilzakka · 2026-09-23
- Ternary Bonsai 2 27B: 5.9GB weights retain ~95% of full-precision reasoning — cephaloform · 2026-09-23
- Qwen 27B runs 24hr unattended on one RTX5090, builds full Postgres-SpringBoot-React spreadsheet app — anglepoiselife · 2026-09-23
- OpenRoboto Shift launches: decentralized egocentric video data network for robot brains — markjeffrey · 2026-09-23
- Engineer describes designing digital circuits that recycle most of their energy — MikePFrank · 2026-09-23
- Cloudflare CTO Dane Knecht makes TIME's 2026 executives list as AI crawlers hit 52% of traffic — dinasaur_404 · 2026-09-23