From: | Tomas Vondra <tomas(at)vondra(dot)me> |
---|---|
To: | Ramakrishna m <ram(dot)pgdb(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Cc: | ravisql09(at)gmail(dot)com |
Subject: | Re: Commit Latency |
Date: | 2025-02-05 12:57:42 |
Message-ID: | 637513a7-04b8-4ae1-aece-052106beeeee@vondra.me |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I think the first thing you should do is verify the performance of the
storage, particularly how long it takes to do fsync. You didn't explain
what kind of storage or filesystem you're using, so hard to say.
It's not clear to me what "resource usage" means exactly, but the fsync
may be slow even when nothing else competes for I/O.
regards
Tomas
On 2/5/25 11:18, Ramakrishna m wrote:
> HI Team,
> I have a system handling *300 TPS*, with resource usage *below 10%*.
> However, I’m noticing *commit latency of around 200ms* for *1% of
> transactions*, occasionally spiking to *1 second*. Since there is no
> significant *I/O pressure*, I’m trying to identify what else might be
> causing this in *PostgreSQL 16*.
>
> Below are the parameters, Version and OS details.
>
> image.png
>
> Regards,
> Ram.
--
Tomas Vondra
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2025-02-05 12:58:51 | Re: Commit Latency |
Previous Message | Michał Kłeczek | 2025-02-05 12:55:51 | Re: Lookup tables |