Re: Rapidly decaying performance repopulating a large table - Mailing list pgsql-general

From David Wilson
Subject Re: Rapidly decaying performance repopulating a large table
Date
Msg-id e7f9235d0804221446k5de18bc6s1b55c8cd3cfd93b3@mail.gmail.com
Whole thread Raw
In response to Re: Rapidly decaying performance repopulating a large table  ("Scott Marlowe" <scott.marlowe@gmail.com>)
Responses Re: Rapidly decaying performance repopulating a large table  (Erik Jones <erik@myemma.com>)
Re: Rapidly decaying performance repopulating a large table  (Tomasz Ostrowski <tometzky@batory.org.pl>)
List pgsql-general
On Tue, Apr 22, 2008 at 5:18 PM, Scott Marlowe <scott.marlowe@gmail.com> wrote:
>
>  Try upping your checkpoint segments.  Some folks find fairly large
>  numbers like 50 to 100 to be helpful.  Each segment = 16Megs, so be
>  sure not to run your system out of drive space while increasing it.
>

Ahh, much more progress. Upping the segments to 50, timeout to 30m and
completion target to 0.9 has improved average copy time to between 2
and 10 seconds, which is definitely an improvement. Thanks for the
help. Any other random thoughts while you're at it? :)

--
- David T. Wilson
david.t.wilson@gmail.com

pgsql-general by date:

Previous
From: "D. Dante Lorenso"
Date:
Subject: Re: How to modify ENUM datatypes?
Next
From: Erik Jones
Date:
Subject: Re: Schema migration tools?