From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Victor Sudakov <vas@sibptus.ru>
To: pgsql-admin@lists.postgresql.org
Subject: Re: pgbouncer logs and its efficiency
Date: Thu, 3 Feb 2022 10:39:09 +0100
Message-ID: <a19711e2-c7b7-28e2-6878-85c996f08ef3@enterprisedb.com> (raw)
In-Reply-To: <YfpEkSZ/TUtZRQe6@admin.sibptus.ru>
References: <YfNtsr+D6JKPmncK@admin.sibptus.ru>
<2d4321bd-0174-42c9-3671-fa9626326d10@enterprisedb.com>
<YfpEkSZ/TUtZRQe6@admin.sibptus.ru>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: peter.eisentraut@enterprisedb.com, vas@sibptus.ru, pgsql-admin@lists.postgresql.org
Subject: Re: pgbouncer logs and its efficiency
In-Reply-To: <a19711e2-c7b7-28e2-6878-85c996f08ef3@enterprisedb.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox