Re: checkpointer continuous flushing - V18

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: checkpointer continuous flushing - V18
Date: 2016-03-11 07:18:00
Message-ID: alpine.DEB.2.10.1603110807430.20663@sto
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


>> As you wish. I thought that understanding the underlying performance model
>> with sequential writes written in chunks is important for the admin, and as
>> this guc would have an impact on performance it should be hinted about,
>> including the limits of its effect where large bases will converge to random
>> io performance. But maybe that is not the right place.
>
> I do agree that that's something interesting to document somewhere. But
> I don't think any of the current places in the documentation are a good
> fit, and it's a topic much more general than the feature we're debating
> here. I'm not volunteering, but a good discussion of storage and the
> interactions with postgres surely would be a significant improvement to
> the postgres docs.

I can only concur!

The "Performance Tips" chapter (II.14) is more user/query oriented. The
"Server Administration" bool (III) does not discuss this much.

There is a wiki about performance tuning, but it is not integrated into
the documentation. It could be a first documentation source.

Also the README in some development directories are very interesting,
although they contains too much details about the implementation.

There has been a lot of presentations over the years, and blog posts.

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2016-03-11 07:24:59 Re: checkpointer continuous flushing
Previous Message Tsunakawa, Takayuki 2016-03-11 06:50:39 Re: [HACKERS] How can we expand PostgreSQL ecosystem?