On 2/7/25 14:00, ravi k wrote:
> Thanks for the suggestions!
>
> It looks the issue is happening at the time of wal creation, does
> wal_init_zero off is good option?
>
It's impossible to say if that option will help, considering how little
info about the system you provided. I suggest you start
PS*, 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
Hello
On 2025-Feb-05, Ramakrishna m wrote:
> 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
On Wed, 2025-02-05 at 15:48 +0530, Ramakrishna m wrote:
> 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 PostgreSQ
he 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*, occa
