From: Scott Carey <scott@richrelevance.com>
To: Alan Hodgson <ahodgson@simkin.ca>
Cc: pgsql-performance@postgresql.org
Subject: Re: Improve COPY performance for large data sets
Date: Wed, 10 Sep 2008 10:51:34 -0700
Message-ID: <a1ec7d000809101051r75f451b4yef92396965453381@mail.gmail.com> (raw)
In-Reply-To: <a1ec7d000809101049k19b56deh9bc212eaede88d79@mail.gmail.com>
References: <48C7FA69.1080507@brightbuilders.com>
<200809101014.34249@hal.medialogik.com>
<a1ec7d000809101049k19b56deh9bc212eaede88d79@mail.gmail.com>
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.
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: scott@richrelevance.com, ahodgson@simkin.ca
Subject: Re: Improve COPY performance for large data sets
In-Reply-To: <a1ec7d000809101051r75f451b4yef92396965453381@mail.gmail.com>
References: <48C7FA69.1080507@brightbuilders.com> <200809101014.34249@hal.medialogik.com> <a1ec7d000809101049k19b56deh9bc212eaede88d79@mail.gmail.com> <a1ec7d000809101051r75f451b4yef92396965453381@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox