16 ms·
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
by chucky_z 8y ago
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.
- iKSv2 8y agoCorrect 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.