Re: Rapidly decaying performance repopulating a large table

From: "David Wilson" <david(dot)t(dot)wilson(at)gmail(dot)com>
To: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Rapidly decaying performance repopulating a large table
Date: 2008-04-22 21:46:42
Message-ID: e7f9235d0804221446k5de18bc6s1b55c8cd3cfd93b3@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Apr 22, 2008 at 5:18 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)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(dot)t(dot)wilson(at)gmail(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Erik Jones 2008-04-22 21:59:32 Re: Schema migration tools?
Previous Message D. Dante Lorenso 2008-04-22 21:34:55 Re: How to modify ENUM datatypes?