From: Scott Marlowe <scott.marlowe@gmail.com>
To: Douglas J Hunley <doug@hunley.homeip.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: which is more important? freq of checkpoints or the duration of them?
Date: Mon, 3 Mar 2008 09:16:34 -0600
Message-ID: <dcc563d10803030716m4592b7beh5c932d91f3ee4dcd@mail.gmail.com> (raw)
In-Reply-To: <200803030925.02931.doug@hunley.homeip.net>
References: <200803030925.02931.doug@hunley.homeip.net>
On Mon, Mar 3, 2008 at 8:25 AM, Douglas J Hunley <doug@hunley.homeip.net> wrote:
> Subject about says it all. Should I be more concerned about checkpoints
> happening 'frequently' or lasting 'longer'? In other words, is it ok to
> checkpoint say, every 5 minutes, if it only last a second or three or better
> to have checkpoints every 10 minutes that last half a minute? Stupid examples
> probably, but you get my point I hope :)
The answer is, of course, it depends.
If you do a lot of batch processing where you move a lot of data in a
stream into the database, then less, but larger checkpoints are
probably a win.
Or is this a transactional system that has to run transactions in
under x seconds? Then more, smaller checkpoints might make sense.
And then, you might be better off using the bgwriter. If tuned
properly, it will keep ahead of your checkpoints just enough that they
never have to happen. Comes with a price, some small % of performance
loss peak, in exchange for a smoother behaviour.
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: scott.marlowe@gmail.com, doug@hunley.homeip.net
Subject: Re: which is more important? freq of checkpoints or the duration of them?
In-Reply-To: <dcc563d10803030716m4592b7beh5c932d91f3ee4dcd@mail.gmail.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