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 A034E53359 for ; Mon, 18 Apr 2005 15:21:07 -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 25480-04 for ; Mon, 18 Apr 2005 18:21:06 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.202]) by svr1.postgresql.org (Postfix) with ESMTP id C6BA653371 for ; Mon, 18 Apr 2005 15:21:04 -0300 (ADT) Received: by wproxy.gmail.com with SMTP id 68so1544516wri for ; Mon, 18 Apr 2005 11:21:06 -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=AmlKQvU4lczINKiXqr+6TJbLmbU0KSYBgsFJf8ofkb6d2P7UCKK1rzvayYnuQ5NOY3fJ0oPkUmuoH9EhpOnZ4kkKCizTX7FVZ+fLLXvX7E8gEObAmSUlSm0eNj5FqxGEUBd7ME8WUAKYDcTC/zrwBXYkSW5/GAJQaKjVTXD910k= Received: by 10.54.32.51 with SMTP id f51mr2500056wrf; Mon, 18 Apr 2005 11:21:04 -0700 (PDT) Received: by 10.54.86.16 with HTTP; Mon, 18 Apr 2005 11:21:04 -0700 (PDT) Message-ID: <33c6269f0504181121385a1f0a@mail.gmail.com> Date: Mon, 18 Apr 2005 14:21:04 -0400 From: Alex Turner Reply-To: Alex Turner To: 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> 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> <6.2.0.14.0.20050418192528.04238088@pop.interactivemediafactory.net> <33c6269f05041811165228c814@mail.gmail.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/421 X-Sequence-Number: 11818 So I wonder if one could take this stripe size thing further and say that a larger stripe size is more likely to result in requests getting served parallized across disks which would lead to increased performance? Again, thanks to all people on this list, I know that I have learnt a _hell_ of alot since subscribing. Alex Turner netEconomist On 4/18/05, Alex Turner wrote: > Ok - well - I am partially wrong... >=20 > If you're stripe size is 64Kb, and you are reading 256k worth of data, > it will be spread across four drives, so you will need to read from > four devices to get your 256k of data (RAID 0 or 5 or 10), but if you > are only reading 64kb of data, I guess you would only need to read > from one disk. >=20 > 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. >=20 > Alex Turner > netEconomist >=20 > On 4/18/05, Jacques Caron wrote: > > Hi, > > > > At 18:56 18/04/2005, Alex Turner wrote: > > >All drives are required to fill every request in all RAID levels > > > > No, this is definitely wrong. In many cases, most drives don't actually > > have the data requested, how could they handle the request? > > > > When reading one random sector, only *one* drive out of N is ever used = to > > service any given request, be it RAID 0, 1, 0+1, 1+0 or 5. > > > > When writing: > > - in RAID 0, 1 drive > > - in RAID 1, RAID 0+1 or 1+0, 2 drives > > - in RAID 5, you need to read on all drives and write on 2. > > > > Otherwise, what would be the point of RAID 0, 0+1 or 1+0? > > > > Jacques. > > > > >