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 E7DF953232 for ; Mon, 18 Apr 2005 15:18:28 -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 24454-02 for ; Mon, 18 Apr 2005 18:18:21 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.200]) by svr1.postgresql.org (Postfix) with ESMTP id 8321A52955 for ; Mon, 18 Apr 2005 15:18:21 -0300 (ADT) Received: by wproxy.gmail.com with SMTP id 68so1543633wri for ; Mon, 18 Apr 2005 11:18:22 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=IdYhJgfvzfxsJ7ooPrsZ2Dm95QmMOK7E34ObEgwirS79ZyZC63/RSbGiBrmULGVKr2mMZ9Vd7CbjB/pwweNb2kLM4XbTnHo0uVcjFBBduQVujyXoWN0QpSD/1gFRXbva4wTI4hAgmFJl5lqB+fXap3AL2sbX6hoPfAFJMGioryI= Received: by 10.54.32.51 with SMTP id f51mr2496264wrf; Mon, 18 Apr 2005 11:18:21 -0700 (PDT) Received: by 10.54.86.16 with HTTP; Mon, 18 Apr 2005 11:18:21 -0700 (PDT) Message-ID: <33c6269f05041811187170139f@mail.gmail.com> Date: Mon, 18 Apr 2005 14:18:21 -0400 From: Alex Turner Reply-To: Alex Turner To: John A Meinel Subject: Re: How to improve db performance with $7K? Cc: Greg Stark , William Yu , pgsql-performance@postgresql.org In-Reply-To: <4263EB5E.8000309@arbash-meinel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <425EBA0C.6030804@sfnet.cc> <87pswsku6e.fsf@stark.xeocode.com> <33c6269f0504180817511b27a3@mail.gmail.com> <878y3gks3p.fsf@stark.xeocode.com> <33c6269f05041809566abf91d2@mail.gmail.com> <4263EB5E.8000309@arbash-meinel.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.276 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200504/419 X-Sequence-Number: 11816 Not true - the recommended RAID level is RAID 10, not RAID 0+1 (at least I would never recommend 1+0 for anything). RAID 10 and RAID 0+1 are _quite_ different. One gives you very good redundancy, the other is only slightly better than RAID 5, but operates faster in degraded mode (single drive). Alex Turner netEconomist On 4/18/05, John A Meinel wrote: > Alex Turner wrote: >=20 > >[snip] > > > > > >>Adding drives will not let you get lower response times than the averag= e seek > >>time on your drives*. But it will let you reach that response time more= often. > >> > >> > >> > >[snip] > > > >I believe your assertion is fundamentaly flawed. Adding more drives > >will not let you reach that response time more often. All drives are > >required to fill every request in all RAID levels (except possibly > >0+1, but that isn't used for enterprise applicaitons). > > > Actually 0+1 is the recommended configuration for postgres databases > (both for xlog and for the bulk data), because the write speed of RAID5 > is quite poor. > Hence you base assumption is not correct, and adding drives *does* help. >=20 > >Most requests > >in OLTP require most of the request time to seek, not to read. Only > >in single large block data transfers will you get any benefit from > >adding more drives, which is atypical in most database applications. > >For most database applications, the only way to increase > >transactions/sec is to decrease request service time, which is > >generaly achieved with better seek times or a better controller card, > >or possibly spreading your database accross multiple tablespaces on > >seperate paritions. > > > > > This is probably true. However, if you are doing lots of concurrent > connections, and things are properly spread across multiple spindles > (using RAID0+1, or possibly tablespaces across multiple raids). > Then each seek occurs on a separate drive, which allows them to occur at > the same time, rather than sequentially. Having 2 processes competing > for seeking on the same drive is going to be worse than having them on > separate drives. > John > =3D:-> >=20 >=20 >