From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
Cc: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: checkpointer continuous flushing - V18 |
Date: | 2016-02-19 22:11:00 |
Message-ID: | 20160219221100.hthdk5yrhtsfgnxf@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2016-02-19 22:46:44 +0100, Fabien COELHO wrote:
>
> Hello Andres,
>
> >Here's the next two (the most important) patches of the series:
> >0001: Allow to trigger kernel writeback after a configurable number of writes.
> >0002: Checkpoint sorting and balancing.
>
> I will look into these two in depth.
>
> Note that I would have ordered them in reverse because sorting is nearly
> always very beneficial, and "writeback" (formely called flushing) is then
> nearly always very beneficial on sorted buffers.
I had it that way earlier. I actually saw pretty large regressions from
sorting alone in some cases as well, apparently because the kernel
submits much larger IOs to disk; although that probably only shows on
SSDs. This way the modifications imo look a trifle better ;). I'm
intending to commit both at the same time, keep them separate only
because they're easier to ynderstand separately.
Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2016-02-20 00:28:12 | Re: checkpointer continuous flushing - V16 |
Previous Message | Fabien COELHO | 2016-02-19 21:46:44 | Re: checkpointer continuous flushing - V18 |