Re: How to analyze of short but heavy intermittent slowdown on BIND on production database (or BIND vs log_lock_waits) - Mailing list pgsql-performance

From Maxim Boguk
Subject Re: How to analyze of short but heavy intermittent slowdown on BIND on production database (or BIND vs log_lock_waits)
Date
Msg-id CAK-MWwRfJk2978FqLMvqmM3e90vq95o2bfnxkrjyC+5_buyWNg@mail.gmail.com
Whole thread Raw
In response to Re: How to analyze of short but heavy intermittent slowdown on BIND on production database (or BIND vs log_lock_waits)  (MichaelDBA <MichaelDBA@sqlexec.com>)
List pgsql-performance

On Sun, Jan 1, 2023 at 6:55 PM MichaelDBA <MichaelDBA@sqlexec.com> wrote:
You said it's a dedicated server, but pgbouncer is running locally, right?  PGBouncer has a small footprint, but is the CPU high for it?

There are 4 pgbouncer processes in so_reuseport mode.
I never saw more than 40% of a single CPU core per one pgbouncer process (most time under 20%).
So it's an unlikely result of pgbouncer being overloaded.

 
--
Maxim Boguk
Senior Postgresql DBA
https://dataegret.com/

Phone UA: +380 99 143 0000
Phone AU: +61  45 218 5678

pgsql-performance by date:

Previous
From: MichaelDBA
Date:
Subject: Re: How to analyze of short but heavy intermittent slowdown on BIND on production database (or BIND vs log_lock_waits)
Next
From: Maxim Boguk
Date:
Subject: Re: How to analyze of short but heavy intermittent slowdown on BIND on production database (or BIND vs log_lock_waits)