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 MichaelDBA
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 49cec5cf-efd5-8be1-cebb-43a6594e07d3@sqlexec.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)  (Maxim Boguk <maxim.boguk@gmail.com>)
Responses Re: How to analyze of short but heavy intermittent slowdown on BIND on production database (or BIND vs log_lock_waits)  (Maxim Boguk <maxim.boguk@gmail.com>)
List pgsql-performance
Hi Maxim,

10-20 active, concurrent connections is way below any CPU load problem you should have with 48 available vCPUs. 
You never explicitly said what the load is, so what is it in the context of the 1,5,15?

Maxim Boguk wrote on 1/1/2023 11:30 AM:
1)usual load (e.g. no anomalies)
10-20 concurrent query runs (e.g. issues isn't related to the load spike or similar anomalies)
additionally 5-10 short idle in transaction (usual amount too)
total around 300 active connections to the database (after local pgbouncer in transaction mode)


Regards,

Michael Vitale

Michaeldba@sqlexec.com

703-600-9343 


Attachment

pgsql-performance by date:

Previous
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)
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)