Message-ID: <a19711e2-c7b7-28e2-6878-85c996f08ef3@enterprisedb.com>
Date: Thu, 3 Feb 2022 10:39:09 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0)
 Gecko/20100101 Thunderbird/91.5.1
Subject: Re: pgbouncer logs and its efficiency
Content-Language: en-US
To: Victor Sudakov <vas@sibptus.ru>, pgsql-admin@lists.postgresql.org
References: <YfNtsr+D6JKPmncK@admin.sibptus.ru>
 <2d4321bd-0174-42c9-3671-fa9626326d10@enterprisedb.com>
 <YfpEkSZ/TUtZRQe6@admin.sibptus.ru>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
In-Reply-To: <YfpEkSZ/TUtZRQe6@admin.sibptus.ru>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/a19711e2-c7b7-28e2-6878-85c996f08ef3%40enterprisedb.com>
Precedence: bulk

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.