From: | Victor Sudakov <vas(at)sibptus(dot)ru> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
Subject: | Re: pgbouncer logs and its efficiency |
Date: | 2022-02-02 08:45:05 |
Message-ID: | YfpEkSZ/TUtZRQe6@admin.sibptus.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)fidonet
From | Date | Subject | |
---|---|---|---|
Next Message | Nikhil Shetty | 2022-02-02 10:17:58 | Lost replication slots after pg_upgrade. |
Previous Message | Holger Jakobs | 2022-02-02 07:16:00 | Re: Determine potential change in table size after a column dropped? |