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>
From: Maxim Boguk <maxim.boguk@gmail.com>
To: MichaelDBA <MichaelDBA@sqlexec.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>,
pgsql-performance@lists.postgresql.org
Date: 2023-01-01T16:51:07Z
Lists: pgsql-performance
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