Re: pgbouncer logs and its efficiency - Mailing list pgsql-admin

From Victor Sudakov
Subject Re: pgbouncer logs and its efficiency
Date
Msg-id YfpEkSZ/TUtZRQe6@admin.sibptus.ru
Whole thread Raw
In response to Re: pgbouncer logs and its efficiency  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: pgbouncer logs and its efficiency  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-admin
Peter Eisentraut wrote:
> On 28.01.22 05:14, Victor Sudakov wrote:
> > 1. What is the meaning of those IDs in the log like
> > "S-0xaaaae460fcb0", "C-0xaaaae45d9fb0" ? I suspect that "S-" and "C-"
> > mean "server" and "client", but what are those HEX numbers?
> 
> These are the internal addresses of the server and client structures. 
> You can use those to track a particular server or client connection 
> through the logs and through SHOW SERVERS and SHOW SERVERS.

I see. So they are probably not very useful for my task.

> 
> > 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.

-- 
Victor Sudakov VAS4-RIPE
http://vas.tomsk.ru/
2:5005/49@fidonet



pgsql-admin by date:

Previous
From: Holger Jakobs
Date:
Subject: Re: Determine potential change in table size after a column dropped?
Next
From: Nikhil Shetty
Date:
Subject: Lost replication slots after pg_upgrade.