Re: Let PostgreSQL's On Schedule checkpoint write buffer smooth spread cycle by tuning IsCheckpointOnSchedule?

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, digoal zhou <digoal(dot)zhou(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Let PostgreSQL's On Schedule checkpoint write buffer smooth spread cycle by tuning IsCheckpointOnSchedule?
Date: 2015-07-02 11:05:54
Message-ID: CAA4eK1Kkf_vFAgfQfatj7mK3KWdoFj2RmDM-6QKo39Mj5Nx-kQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 2, 2015 at 4:16 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:

> On 13 May 2015 at 09:35, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
>
>
>> In summary, the X^1.5 correction seems to work pretty well. It doesn't
>> completely eliminate the problem, but it makes it a lot better.
>>
>
> Agreed
>

Do we want to consider if wal_compression is enabled as that
can reduce the effect full_page_writes?

Also I am planning to run some tests for this patch, but not sure
if tps and or latency numbers by pgbench are sufficient or do you
people want to see actual read/write count via some form of
dynamic tracing (stap) as done by the reporter of this issue?

With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2015-07-02 11:14:59 Re: raw output from copy
Previous Message Fujii Masao 2015-07-02 11:02:12 pg_archivecleanup, and backup filename to specify as an argument