Search Postgresql Archives

Re: Rapidly decaying performance repopulating a large table

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Apr 22, 2008, at 4:46 PM, David Wilson wrote:

On Tue, Apr 22, 2008 at 5:18 PM, Scott Marlowe <scott.marlowe@xxxxxxxxx > 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? :)

Has anyone yet pointed out the standards: drop indexes and foreign keys and rebuild them once the entire data import is finished?

Erik Jones

DBA | Emma®
erik@xxxxxxxxxx
800.595.4401 or 615.292.5888
615.292.0777 (fax)

Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux