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 - V16 |
Date: | 2016-02-04 15:54:58 |
Message-ID: | 20160204155458.jrw3crmyscusdqf6@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
Fabien asked me to post a new version of the checkpoint flushing patch
series. While this isn't entirely ready for commit, I think we're
getting closer.
I don't want to post a full series right now, but my working state is
available on
http://git.postgresql.org/gitweb/?p=users/andresfreund/postgres.git;a=shortlog;h=refs/heads/checkpoint-flush
git://git.postgresql.org/git/users/andresfreund/postgres.git checkpoint-flush
The main changes are that:
1) the significant performance regressions I saw are addressed by
changing the wal writer flushing logic
2) The flushing API moved up a couple layers, and now deals with buffer
tags, rather than the physical files
3) Writes from checkpoints, bgwriter and files are flushed, configurable
by individual GUCs. Without that I still saw the spiked in a lot of circumstances.
There's also a more experimental reimplementation of bgwriter, but I'm
not sure it's realistic to polish that up within the constraints of 9.6.
Regards,
Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2016-02-04 16:25:55 | Re: [WIP] Effective storage of duplicates in B-tree index. |
Previous Message | Fabien COELHO | 2016-02-04 15:53:55 | Re: pgbench stats per script & other stuff |