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

From: MichaelDBA <MichaelDBA(at)sqlexec(dot)com>
To: Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: How to analyze of short but heavy intermittent slowdown on BIND on production database (or BIND vs log_lock_waits)
Date: 2023-01-01 16:43:10
Message-ID: 49cec5cf-efd5-8be1-cebb-43a6594e07d3@sqlexec.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)sqlexec(dot)com <mailto:michaelvitale(at)sqlexec(dot)com>

703-600-9343

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Maxim Boguk 2023-01-01 16:51:07 Re: How to analyze of short but heavy intermittent slowdown on BIND on production database (or BIND vs log_lock_waits)
Previous Message Maxim Boguk 2023-01-01 16:30:55 Re: How to analyze of short but heavy intermittent slowdown on BIND on production database (or BIND vs log_lock_waits)