Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 96C079FB3A0 for ; Wed, 25 Oct 2006 13:34:33 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 02713-02 for ; Wed, 25 Oct 2006 13:34:32 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from exprod6og50.obsmtp.com (exprod6og50.obsmtp.com [64.18.1.181]) by postgresql.org (Postfix) with SMTP id 244999FB250 for ; Wed, 25 Oct 2006 13:34:31 -0300 (ADT) Received: from source ([63.240.6.44]) by exprod6ob50.postini.com ([64.18.5.12]) with SMTP; Wed, 25 Oct 2006 09:34:20 PDT Received: from 172.16.1.239 by mail.mi8.com with ESMTP (- Welcome to Mi8 Corporation www.Mi8.com (D4)); Wed, 25 Oct 2006 12:34:09 -0400 X-Server-Uuid: C8FB4D43-1108-484A-A898-3CBCC7906230 Received: from MI8NYCMAIL06.Mi8.com ([172.16.1.175]) by d01smtp06.Mi8.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Oct 2006 12:34:04 -0400 Received: from 69.181.100.71 ([69.181.100.71]) by MI8NYCMAIL06.Mi8.com ( [172.16.1.219]) via Exchange Front-End Server mi8owa.mi8.com ( [172.16.1.105]) with Microsoft Exchange Server HTTP-DAV ; Wed, 25 Oct 2006 16:34:04 +0000 User-Agent: Microsoft-Entourage/11.2.5.060620 Date: Wed, 25 Oct 2006 09:34:01 -0700 Subject: Re: Best COPY Performance From: "Luke Lonergan" To: "Merlin Moncure" , "Worky Workerson" cc: "Markus Schaber" , pgsql-performance@postgresql.org Message-ID: Thread-Topic: [PERFORM] Best COPY Performance Thread-Index: Acb4U2BnnrjeimRGEduYOAAWy4o9DA== In-Reply-To: MIME-Version: 1.0 X-OriginalArrivalTime: 25 Oct 2006 16:34:04.0518 (UTC) FILETIME=[62803060:01C6F853] X-WSS-ID: 69214E7C2TS3094454-08-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200610/521 X-Sequence-Number: 21650 Merlin, On 10/25/06 8:38 AM, "Merlin Moncure" wrote: > in theory, with 10 10k disks in raid 10, you should be able to keep > your 2fc link saturated all the time unless your i/o is extremely > random. random i/o is the wild card here, ideally you should see at > least 2000 seeks in bonnie...lets see what comes up. The 2000 seeks/sec are irrelevant to Postgres with one user doing COPY. Because the I/O is single threaded, you will get one disk worth of seeks for one user, roughly 150/second on a 10K RPM drive. I suspect the problem here is the sequential I/O rate - let's wait and see what the dd test results look like. - Luke