We scaled PgBouncer to 4x throughput

228 points · 53 comments on HN · read original →

Points and comments are a snapshot, not live.

Article body wasn't reachable. The HN discussion summary is below.

What commenters are saying

Commenters provide configuration details for SO_REUSEPORT peering and discuss alternatives like HAProxy, Odyssey, and pgdog. Peering forwards cancellation requests between PgBouncer processes to avoid dropped cancels. Some question why Postgres itself doesn't handle connection pooling natively, citing its process-per-connection model. A mention of geopolitical concerns about Russian software (Odyssey, Nginx, ClickHouse) draws pushback.