Re: pgbouncer best practices
От | Rita |
---|---|
Тема | Re: pgbouncer best practices |
Дата | |
Msg-id | CAOF-Kfiwx0AfH8Kvwj4uqTP3USW4hNSOGM1eAJtYia9otmxu-Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pgbouncer best practices (Ben Chobot <bench@silentmedia.com>) |
Ответы |
Re: pgbouncer best practices
|
Список | pgsql-general |
I am not sure if it allows transaction pooling.
On Fri, Jul 7, 2023 at 12:37 PM Ben Chobot <bench@silentmedia.com> wrote:
Rita wrote on 7/7/23 9:23 AM:I have an application that does many db calls from a server farm. I've increased my max connections on postgresql to 1000 and tuned the server accordingly. However, I still get can't connect to postgresql some times. I installed pgbouncer on few servers in the farm. I pointed the traffic to pgbouncer and things helped dramatically. My question are: is there a ratio of max connections and pool i should use in my pgbouncer config?
Does your application allow for transaction pooling? pgBouncer can unlock a lot more efficiency if you can cycle server slots on transaction boundaries.
--- Get your facts first, then you can distort them as you please.--
В списке pgsql-general по дате отправления: