From: Greg Smith <greg@2ndquadrant.com>
To: Sam Nelson <samn@consistentstate.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Checkpoint and Background Writer Statistics
Date: Tue, 22 Feb 2011 19:38:26 -0500
Message-ID: <4D645702.40203@2ndquadrant.com> (raw)
In-Reply-To: <AANLkTikHjPw85v0_5yGy5xNcV3=oR2kX=bXmmH0=3uO-@mail.gmail.com>
References: <AANLkTikHjPw85v0_5yGy5xNcV3=oR2kX=bXmmH0=3uO-@mail.gmail.com>
Sam Nelson wrote:
> One of our clients has an lru_max_dirty setting of 1000 and a
> bgwriter_delay of 200, but we're still seeing much higher growth in
> the buffers_checkpoint than buffers_clean, with buffers_checkpoint
> increasing at about 20 times the rate that buffers_clean is. We don't
> see very much growth in the maxwritten_clean, though - something like
> one every couple of days.
The background writer can only clean data pages that haven't been used
in a while. In your case, it sounds like most of the things that are
getting dirty are being touched enough that they never meet its
criteria. There's nothing wrong with that. Writing out dirty buffers
only once per checkpoint is in theory the most efficient way to handle
regularly changed data.
--
Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
"PostgreSQL 9.0 High Performance": http://www.2ndQuadrant.com/books
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-admin@postgresql.org
Cc: greg@2ndquadrant.com, samn@consistentstate.com
Subject: Re: Checkpoint and Background Writer Statistics
In-Reply-To: <4D645702.40203@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