From: Jim C. Nasby <decibel@decibel.org>
To: daveg <daveg@sonic.net>
Cc: Greg Smith <gsmith@gregsmith.com>
Cc: pgsql-patches@postgresql.org
Subject: Re: Automatic adjustment of bgwriter_lru_maxpages
Date: Tue, 15 May 2007 19:08:07 -0500
Message-ID: <20070516000807.GF20707@nasby.net> (raw)
In-Reply-To: <20070515045516.GE2359@sonic.net>
References: <461E108D.6080709@enterprisedb.com>
<Pine.GSO.4.64.0705121926420.9615@westnet.com>
<20070514174531.71E0.ITAGAKI.TAKAHIRO@oss.ntt.co.jp>
<Pine.GSO.4.64.0705140926470.9478@westnet.com>
<9814.1179150750@sss.pgh.pa.us>
<Pine.GSO.4.64.0705140957360.9478@westnet.com>
<20070515045516.GE2359@sonic.net>
Moving to -performance.
On Mon, May 14, 2007 at 09:55:16PM -0700, daveg wrote:
> Apologies for asking this on the wrong list, but it is at least the right
> thread.
>
> What is the current thinking on bg_writer setttings for systems such as
> 4 core Opteron with 16GB or 32GB of memory and heavy batch workloads?
It depends greatly on how much of your data tends to stay 'pinned' in
shared_buffers between checkpoints. In a case where the same data tends
to stay resident you're going to need to depend on the 'all' scan to
decrease the impact of checkpoints (though the load distributed
checkpoint patch will change that greatly).
Other than that tuning bgwriter boils down to your IO capability as well
as how often you're checkpointing.
--
Jim Nasby decibel@decibel.org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
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: decibel@decibel.org, daveg@sonic.net, gsmith@gregsmith.com, pgsql-patches@postgresql.org
Subject: Re: Automatic adjustment of bgwriter_lru_maxpages
In-Reply-To: <20070516000807.GF20707@nasby.net>
* 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