On 2016-01-07 21:08:10 +0100, Fabien COELHO wrote: > Hmmm. What I understood is that the workloads that have some performance > regressions (regressions that I have *not* seen in the many tests I ran) are > not due to checkpointer IOs, but rather in settings where most of the writes > is done by backends or bgwriter.
As far as I can see you've not run many tests where the hot/warm data set is larger than memory (the full machine's memory, not shared_buffers). That quite drastically alters the performance characteristics here, because you suddenly have lots of synchronous read IO thrown into the mix. Whether it's bgwriter or not I've not fully been able to establish, but it's a working theory. > I do not see the point of rewriting the checkpointer for them, although > obviously I agree that something has to be done also for the other > processes. Rewriting the checkpointer and fixing the flush interface in a more generic way aren't the same thing at all. Greetings, Andres Freund -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
