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 |
Date: | 2016-03-11 01:34:26 |
Message-ID: | 20160311013426.7fjjhyasxubmam2x@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
I just pushed the two major remaining patches in this thread. Let's see
what the buildfarm has to say; I'd not be surprised if there's some
lingering portability problem in the flushing code.
There's one remaining issue we definitely want to resolve before the
next release: Right now we always use one writeback context across all
tablespaces in a checkpoint, but Fabien's testing shows that that's
likely to hurt in a number of cases. I've some data suggesting the
contrary in others.
Things that'd be good:
* Some benchmarking. Right now controlled flushing is enabled by default
on linux, but disabled by default on other operating systems. Somebody
running benchmarks on e.g. freebsd or OSX might be good.
* If somebody has the energy to provide a windows implemenation for
flush control, that might be worthwhile. There's several places that
could benefit from that.
* The default values are basically based on benchmarking by me and Fabien.
Regards,
Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Dilip Kumar | 2016-03-11 01:44:21 | Re: Relation extension scalability |
Previous Message | Joel Jacobson | 2016-03-11 01:31:56 | Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity. |