Skip site navigation (1) Skip section navigation (2)

Re: Best COPY Performance

From: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
To: Worky Workerson <worky(dot)workerson(at)gmail(dot)com>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>,Markus Schaber <schabi(at)logix-tt(dot)com>,pgsql-performance(at)postgresql(dot)org
Subject: Re: Best COPY Performance
Date: 2006-10-26 03:34:48
Message-ID: 20061026033448.GC26892@nasby.net (view raw or flat)
Thread:
Lists: pgsql-performance
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(at)nasby(dot)net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)

In response to

Responses

pgsql-performance by date

Next:From: Jim C. NasbyDate: 2006-10-26 04:21:50
Subject: Re: commit so slow program looks frozen
Previous:From: Joshua D. DrakeDate: 2006-10-25 22:12:00
Subject: Re: commit so slow program looks frozen

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group