Re: Let PostgreSQL's On Schedule checkpoint write buffer smooth spread cycle by tuning IsCheckpointOnSchedule? - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: Let PostgreSQL's On Schedule checkpoint write buffer smooth spread cycle by tuning IsCheckpointOnSchedule?
Date
Msg-id alpine.DEB.2.10.1507030930070.16176@sto
Whole thread Raw
In response to Re: Let PostgreSQL's On Schedule checkpoint write buffer smooth spread cycle by tuning IsCheckpointOnSchedule?  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
> power 1,5 is almost certainly not right for all cases, but it is simple 
> and better.

It is better "in some cases", as I've been told on my patch. If you have a 
separate disk for WAL writes the power formula may just degrade 
performance, or maybe not, or not too much, or it really should be a guc.

Well, I just think that it needs more performance testing with various 
loads and sizes, really. I'm not against this patch at all.

> And easy to remove if something even better arrives.
>
> I don't see the two patches being in conflict.

They are not "in conflict" from a git point of view, or even so it would 
be trivial to solve.

They are in conflict as the patch changes the checkpoint load 
significantly, which would mean that my X00 hours of performance testing 
on the checkpoint scheduler should more or less be run again. Ok, it is 
somehow egoistic, but I'm trying to avoid wasting people time.

Another point is that I'm not sure I understand the decision process: for 
some patch in some area extensive performance tests are required, and for 
other patches in the same area they would not be.

-- 
Fabien.



pgsql-hackers by date:

Previous
From: Beena Emerson
Date:
Subject: Re: Support for N synchronous standby servers - take 2
Next
From: Heikki Linnakangas
Date:
Subject: Re: PATCH: remove nclients/nthreads constraint from pgbench