X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id BDA74D1B551 for ; Fri, 12 Sep 2003 11:06:53 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 55530-06 for ; Fri, 12 Sep 2003 08:06:24 -0300 (ADT) Received: from wight.ymogen.net (unknown [217.27.240.153]) by svr1.postgresql.org (Postfix) with SMTP id D9F8CD1B540 for ; Fri, 12 Sep 2003 08:06:20 -0300 (ADT) Received: (qmail 31808 invoked from network); 12 Sep 2003 11:06:18 -0000 Received: from host213-123-217-162.in-addr.btopenworld.com (HELO solent) (213.123.217.162) by wight.ymogen.net with SMTP; 12 Sep 2003 11:06:18 -0000 From: "Matt Clark" To: , Subject: Re: best arrangement of 3 disks for (insert) performance Date: Fri, 12 Sep 2003 12:06:12 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: <200309121126.29756.rj@last.fm> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/195 X-Sequence-Number: 3561 > the machine will be dealing with lots of inserts, basically as many as we can > throw at it If you mean lots of _transactions_ with few inserts per transaction you should get a RAID controller w/ battery backed write-back cache. Nothing else will improve your write performance by nearly as much. You could sell the RAM and one of the CPU's to pay for it ;-) If you have lots of inserts but all in a few transactions then it's not quite so critical. M