| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Victor Sudakov <vas(at)sibptus(dot)ru>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgbouncer logs and its efficiency |
| Date: | 2022-02-03 09:39:09 |
| Message-ID: | a19711e2-c7b7-28e2-6878-85c996f08ef3@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 02.02.22 09:45, Victor Sudakov wrote:
>>> 2. How would you calculate the efficiency of pgbouncer, like
>>> client_conns/server_conns ratio (current and average over over time)?
>>
>> This depends heavily on what you are using pgbouncer for and what
>> metrics are relevant for your application.
>
> The relevant metric would be the client_conns/server_conns ratio. If
> there have been 1000 client connections/disconnections and they have
> caused only 100 new backends to start, I'd consider it a good ratio.
>
> The question is how to estimate it.
You can count the number of rows in the SHOW CLIENTS and SHOW SERVERS
output and chart them using your favorite metrics collection system.
There are various tools and recipes out there on how to collect metrics
from pgbouncer and push them into metrics or graphing systems.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Victor Sudakov | 2022-02-03 15:15:44 | Re: pgbouncer logs and its efficiency |
| Previous Message | Victor Sudakov | 2022-02-03 07:26:47 | Re: Lost replication slots after pg_upgrade. |