Gracefully Scaling to 10k PostgreSQL Connections for $35/mo, Part Two

Re:Gracefully Scaling to 10k PostgreSQL Connections for $35/... by chucky_z on Friday June 22, 2018 @02:30AM (#17371865)

I'm glad that pretty much the whole thing is 'use pgbouncer.'

This was my exact situation at a previous position. We needed up to 20k connections to a single pgsql master. Even the most monster postgres server falls over around ~600 connections (up to 1k depending on usage).

Using a pgbouncer-per-webserver we easily got to 20k.

I will say this was with 9.3 though, things may have changed on that front. Nowadays I use pgsql primarily for analytics, so there's only ever 20-30 connections tops, albeit doing quite heavy querying.

[ Parent | on HN ]

Re:Gracefully Scaling to 10k PostgreSQL Connections for $35/... by iKSv2 on Friday June 22, 2018 @03:38AM (#17372181)

Correct me if I am wrong in understanding this "Using a pgbouncer-per-webserver we easily got to 20k.", but does this mean say you have 5 web-servers, each web-server has an instance of pgbouncer installed? or you have 5 web-servers with 5 separate pgbouncer servers (1:1 mapping between webserver and pgbouncer) while all pgbouncer server transact with a powerful, single master Postgres.

[ Parent | on HN ]