From: Jim C. Nasby <jim@nasby.net>
To: Worky Workerson <worky.workerson@gmail.com>
Cc: Merlin Moncure <mmoncure@gmail.com>
Cc: Markus Schaber <schabi@logix-tt.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Best COPY Performance
Date: Wed, 25 Oct 2006 22:34:48 -0500
Message-ID: <20061026033448.GC26892@nasby.net> (raw)
In-Reply-To: <ce4072df0610250825h324d30datece27c0c541162ff@mail.gmail.com>
References: <ce4072df0610201305u7836dc7bn437ec0aaf1c3e25f@mail.gmail.com>
<453C8B0D.4070803@logix-tt.com>
<ce4072df0610230840r4b3df653h3144dab06bdb9ed2@mail.gmail.com>
<b42b73150610250620r37cf9269m7b6e43b9835bdbcf@mail.gmail.com>
<ce4072df0610250825h324d30datece27c0c541162ff@mail.gmail.com>
On Wed, Oct 25, 2006 at 11:25:01AM -0400, Worky Workerson wrote:
> >I'm guessing the high bursts are checkpoints. Can you check your log
> >files for pg and see if you are getting warnings about checkpoint
> >frequency? You can get some mileage here by increasing wal files.
>
> Nope, nothing in the log. I have set:
> wal_buffers=128
> checkpoint_segments=128
> checkpoint_timeout=3000
> which I thought was rather generous. Perhaps I should set it even
> higher for the loads?
But depending on your shared_buffer and bgwriter settings (as well as
how much WAL traffic you're generating, you could still end up with big
slugs of work to be done when checkpoints happen.
If you set checkpoint_warning to 3001, you'll see exactly when
checkpoints are happening, so you can determine if that's an issue.
--
Jim Nasby jim@nasby.net
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: jim@nasby.net, worky.workerson@gmail.com, mmoncure@gmail.com, schabi@logix-tt.com
Subject: Re: Best COPY Performance
In-Reply-To: <20061026033448.GC26892@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