Re: postgresql latency & bgwriter not doing its job - Mailing list pgsql-hackers

From Aidan Van Dyk
Subject Re: postgresql latency & bgwriter not doing its job
Date
Msg-id CAC_2qU9ePZEh=T5Jm8HonrwT2BZ-j-7FQvXv6dV4Zm6yr1OqPA@mail.gmail.com
Whole thread Raw
In response to Re: postgresql latency & bgwriter not doing its job  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: postgresql latency & bgwriter not doing its job
Re: postgresql latency & bgwriter not doing its job
Re: postgresql latency & bgwriter not doing its job
List pgsql-hackers
On Wed, Aug 27, 2014 at 3:32 AM, Fabien COELHO <coelho@cri.ensmp.fr> wrote:

Hello Andres,

[...]

I think you're misunderstanding how spread checkpoints work.

Yep, definitely:-) On the other hand I though I was seeking something "simple", namely correct latency under small load, that I would expect out of the box.

What you describe is reasonable, and is more or less what I was hoping for, although I thought that bgwriter was involved from the start and checkpoint would only do what is needed in the end. My mistake.


If all you want is to avoid the write storms when fsyncs start happening on slow storage, can you not just adjust the kernel vm.dirty* tunables to start making the kernel write out dirty buffers much sooner instead of letting them accumulate until fsyncs force them out all at once?

a.


--
Aidan Van Dyk                                             Create like a god,
aidan@highrise.ca                                       command like a king,
http://www.highrise.ca/                                   work like a slave.

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Hardening pg_upgrade
Next
From: Heikki Linnakangas
Date:
Subject: Re: pgbench throttling latency limit