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 53FA7D1C96C for ; Mon, 24 Nov 2003 04:30:30 +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 70237-09 for ; Mon, 24 Nov 2003 00:29:59 -0400 (AST) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id BA25AD1C951 for ; Mon, 24 Nov 2003 00:29:58 -0400 (AST) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3966870; Sun, 23 Nov 2003 20:30:44 -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: Sun, 23 Nov 2003 20:29:04 -0800 User-Agent: KMail/1.4.3 References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200311232029.04120.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/203 X-Sequence-Number: 4763 William, > I already have fsync off. Short of buying more hardware -- which I will > probably do anyways once I figure out whether I need more CPU, memory or > disk -- what else can I do to max out the speed? Operation mix is about > 50% select, 40% insert, 10% update. Disk. Multi-channel RAID is where it's at, and/or RAID with a great write cache enabled. For really fast updates, I'd suggest 6-disk or even 8-disk RAID 1+0. As soon as you have gobs of extra disk space, jack your checkpoint_buffers way up, like a couple of gigs. -- Josh Berkus Aglio Database Solutions San Francisco