Re: Disk latency goes up during certaing pediods

From: German Becker <german(dot)becker(at)gmail(dot)com>
To: bricklen <bricklen(at)gmail(dot)com>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Disk latency goes up during certaing pediods
Date: 2013-07-30 15:35:02
Message-ID: CALyjCLv0eQVNd1Xd3FJ+smDkeo05LxF0LXh1-_Dpq7hKF_JcyQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

256 was set some time when we were testing a differnt issue. I read that
the only drawback is the amunt of time required for recovery, which was
tested and it was like 10 seconds for the 256 segments, and higher values
mean less disk usage.
Anyway all these parameters should affect the throughput to the data disks,
not the WAL, Am I right?

On Mon, Jul 29, 2013 at 6:07 PM, bricklen <bricklen(at)gmail(dot)com> wrote:

>
> On Mon, Jul 29, 2013 at 1:28 PM, German Becker <german(dot)becker(at)gmail(dot)com>wrote:
>
>> checkpoint_segments = 256 # in logfile segments, min 1,
>> 16MB each
>>
>
>
> I'm curious about checkpoint_segments. 256 seems pretty high -- did
> testing show that that helps?
>
>
>
>> checkpoint_completion_target = 0.7 # checkpoint target duration,
>> 0.0 - 1.0
>>
>
> 0.7 could be bumped up to 0.9, but I doubt that that will make a very
> noticeable difference for this particular issue.
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message bricklen 2013-07-30 16:02:26 Re: Disk latency goes up during certaing pediods
Previous Message Manish Kediyal 2013-07-30 04:41:22 Re: Shell Script for Vacuum