Re: Improve COPY performance for large data sets

From: "Scott Carey" <scott(at)richrelevance(dot)com>
To: "Alan Hodgson" <ahodgson(at)simkin(dot)ca>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Improve COPY performance for large data sets
Date: 2008-09-10 17:51:34
Message-ID: a1ec7d000809101051r75f451b4yef92396965453381@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Correction --
2 hours to read the whole disk.

1. It won't make a load take 12 hours unless we're talking a load that is in
> total, similar to the size of the disk. A slow, newer SATA drive will read
> and write at at ~50MB/sec at minimum, so the whole 320GB can be scanned at
> 3GB per minute. Thats ~ 5 hours. It is not likely that 20M records is over
> 20GB, and at that size there is no way the disk is the bottleneck.
>

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Scott Carey 2008-09-10 17:55:26 Re: too many clog files
Previous Message Scott Carey 2008-09-10 17:49:22 Re: Improve COPY performance for large data sets