Postgres Pro
Downloads
Home   >   mailing lists

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-MWwSDSKoL+8mwYyZA_pfbe6URigtwDwFXd2BY8vEJHS4GdQ@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>)
Responses Re: How to analyze of short but heavy intermittent slowdown on BIND on production database (or BIND vs log_lock_waits)
List pgsql-performance
Tree view


On Sun, Jan 1, 2023 at 6:43 PM MichaelDBA <MichaelDBA@sqlexec.com> wrote:
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?


LA 10-15 all time, servers are really overprovisioned (2-3x by available CPU resources) because an application is quite sensitive to the database latency.
And during these latency spikes - EXECUTE work without any issues (e.g. only PARSE/BIND suck).


--
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: MichaelDBA
Date:
Subject: Re: How to analyze of short but heavy intermittent slowdown on BIND on production database (or BIND vs log_lock_waits)