Skip site navigation (1) Skip section navigation (2)

Re: checkpoint_timeout

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: "Rafael Domiciano" <rafael(dot)domiciano(at)gmail(dot)com>, "Julio Leyva" <jcleyva(at)hotmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: checkpoint_timeout
Date: 2008-10-08 18:16:33
Message-ID: dcc563d10810081116g6aece154rbadf99951ab4caa2@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
On Wed, Oct 8, 2008 at 12:08 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
>
> If the problem is checkpoints (which seems likely but far from a sure
> thing based on the information provided), aggressive background writer
> setting might be your best bet under 8.2.X.  To solve similar problems
> we had to go to the following, although many on these lists feel that
> settings this aggressive are rarely needed, so use at your own risk.
>
> #bgwriter_delay = 200ms
> bgwriter_lru_percent = 20.0
> bgwriter_lru_maxpages = 200
> bgwriter_all_percent = 10.0
> bgwriter_all_maxpages = 600

I've tuned an 8.2 server with settings similar to this, and it made a
world of difference on smoothing out performance.  Note that bgwriter
tends to use cpu and memory bandwidth up, so avoid going crazy on it.

> Even better would be to go to the latest revision of the 8.3 release,
> which at this writing is 8.3.4.  In that release PostgreSQL spreads
> out the work of a checkpoint to minimize this problem.

Seconded.  A lot of hard work went into making the bgwriter much
easier to adjust, and much less likely to even need adjusting in 8.3.

In response to

Responses

pgsql-admin by date

Next:From: Scott MarloweDate: 2008-10-08 18:28:54
Subject: Re: replication with table add/removes..
Previous:From: Kevin GrittnerDate: 2008-10-08 18:08:46
Subject: Re: checkpoint_timeout

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group