Re: pgbouncer best practices

From: Ben Chobot <bench(at)silentmedia(dot)com>
To: Rita <rmorgan466(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org>
Subject: Re: pgbouncer best practices
Date: 2023-07-07 16:37:33
Message-ID: d3b0685f-5e6c-5f1f-2379-3947a6cc2e0a@silentmedia.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Gurjeet Singh 2023-07-07 18:09:33 Re: pgbouncer best practices
Previous Message Rita 2023-07-07 16:23:42 pgbouncer best practices