From: Greg Smith <greg@2ndQuadrant.com>
To: pgsql-performance@postgresql.org
Subject: Re: : PG9.0 - Checkpoint tuning and pg_stat_bgwriter
Date: Tue, 04 Oct 2011 15:32:00 -0700
Message-ID: <4E8B8960.9030903@2ndQuadrant.com> (raw)
In-Reply-To: <CAFrxt0iXn1vzF0wBzva+8CSdK34iqJ+mzcucxGpWqZ5s77LjXQ@mail.gmail.com>
References: <CAFrxt0iXn1vzF0wBzva+8CSdK34iqJ+mzcucxGpWqZ5s77LjXQ@mail.gmail.com>
On 10/04/2011 03:50 AM, Venkat Balaji wrote:
> I had a look at the pg_stat_bgwriter as well.
Try saving it like this instead:
select now(),* from pg_stat_bgwriter;
And collect two data points, space a day or more apart. That gives a
lot more information about the rate at which things are actually
happening. The long-term totals are less interesting than that.
Generally the first round of tuning work here is to increase
checkpoint_segments until most checkpoints appear in checkpoints_timed
rather than checkpoints_req. After that, increasing checkpoint_timeout
might also be useful.
--
Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: greg@2ndQuadrant.com
Subject: Re: : PG9.0 - Checkpoint tuning and pg_stat_bgwriter
In-Reply-To: <4E8B8960.9030903@2ndQuadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox