From: | Rita <rmorgan466(at)gmail(dot)com> |
---|---|
To: | Ben Chobot <bench(at)silentmedia(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-08 11:27:10 |
Message-ID: | CAOF-Kfiwx0AfH8Kvwj4uqTP3USW4hNSOGM1eAJtYia9otmxu-Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I am not sure if it allows transaction pooling.
On Fri, Jul 7, 2023 at 12:37 PM Ben Chobot <bench(at)silentmedia(dot)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.--
From | Date | Subject | |
---|---|---|---|
Next Message | Ben Chobot | 2023-07-08 13:46:37 | Re: pgbouncer best practices |
Previous Message | Gurjeet Singh | 2023-07-07 18:09:33 | Re: pgbouncer best practices |