X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 9DC62D1C943 for ; Mon, 24 Nov 2003 17:27:27 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 76321-06 for ; Mon, 24 Nov 2003 13:26:56 -0400 (AST) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 4A961D1B531 for ; Mon, 24 Nov 2003 13:26:55 -0400 (AST) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3969930; Mon, 24 Nov 2003 09:27:42 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Organization: Aglio Database Solutions To: William Yu , pgsql-performance@postgresql.org Subject: Re: Maximum Possible Insert Performance? Date: Mon, 24 Nov 2003 09:25:58 -0800 User-Agent: KMail/1.4.3 References: <3FC19C2C.4050704@myrealbox.com> In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200311240925.58070.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/210 X-Sequence-Number: 4770 William, > When my current job batch is done, I'll save a copy of the dir and give > the WAL on ramdrive a test. And perhaps even buy a Sandisk at the local > store and run that through the hooper. We'll be interested in the results. The Sandisk won't be much of a performance test; last I checked, their access speed was about 1/2 that of a fast SCSI drive. But it could be a feasability test for the more expensive RAMdrive approach. -- Josh Berkus Aglio Database Solutions San Francisco