X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 50F955334B for ; Mon, 18 Apr 2005 15:28:40 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 27651-03 for ; Mon, 18 Apr 2005 18:28:37 +0000 (GMT) Received: from mars.interactivemediafactory.net (mars.imfeurope.net [194.2.222.161]) by svr1.postgresql.org (Postfix) with ESMTP id A0AA553346 for ; Mon, 18 Apr 2005 15:28:35 -0300 (ADT) Received: from JC-8600.directinfos.com (localhost [127.0.0.1]) by mars.interactivemediafactory.net (8.12.11/8.12.11) with ESMTP id j3IISOrV007934; Mon, 18 Apr 2005 20:28:25 +0200 (CEST) (envelope-from jc@directinfos.com) Message-Id: <6.2.0.14.0.20050418202039.03f12008@wheresmymailserver.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Mon, 18 Apr 2005 20:24:25 +0200 To: Alex Turner From: Jacques Caron Subject: Re: How to improve db performance with $7K? Cc: Greg Stark , William Yu , pgsql-performance@postgresql.org In-Reply-To: <33c6269f05041811165228c814@mail.gmail.com> References: <425EBA0C.6030804@sfnet.cc> <87pswsku6e.fsf@stark.xeocode.com> <33c6269f0504180817511b27a3@mail.gmail.com> <878y3gks3p.fsf@stark.xeocode.com> <33c6269f05041809566abf91d2@mail.gmail.com> <6.2.0.14.0.20050418192528.04238088@pop.interactivemediafactory.net> <33c6269f05041811165228c814@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200504/423 X-Sequence-Number: 11820 Hi, At 20:16 18/04/2005, Alex Turner wrote: >So my assertion that adding more drives doesn't help is pretty >wrong... particularly with OLTP because it's always dealing with >blocks that are smaller that the stripe size. When doing random seeks (which is what a database needs most of the time), the number of disks helps improve the number of seeks per second (which is the bottleneck in this case). When doing sequential reads, the number of disks helps improve total throughput (which is the bottleneck in that case). In short: in always helps :-) Jacques.