X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id D7EFD9FB25B for ; Thu, 24 Aug 2006 17:04:01 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 33809-05 for ; Thu, 24 Aug 2006 20:03:42 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.195]) by postgresql.org (Postfix) with ESMTP id C805D9FB24D for ; Thu, 24 Aug 2006 17:03:41 -0300 (ADT) Received: by nz-out-0102.google.com with SMTP id 14so402998nzn for ; Thu, 24 Aug 2006 13:03:40 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Us0y7m2V/sAxOsNV20nVmKIj8IAT9U4SU5hfDgPGuvodVvIfwrceT+jZ87bx/80yKlJDR6FbsFqGc954KI7kJENueZqqNmoDe9PtHgvppQUIY0mf/KpzQLvB1pzBu6HycDZP9HyneJMdPY44kdaWjTz8l8XqfGEFmTUTUPJ1X9Q= Received: by 10.64.204.3 with SMTP id b3mr2709853qbg; Thu, 24 Aug 2006 13:03:39 -0700 (PDT) Received: by 10.65.137.12 with HTTP; Thu, 24 Aug 2006 13:03:39 -0700 (PDT) Message-ID: Date: Thu, 24 Aug 2006 16:03:39 -0400 From: "Merlin Moncure" To: "Scott Marlowe" Subject: Re: PowerEdge 2950 questions Cc: "Jeff Davis" , "Bucky Jordan" , pgsql-performance@postgresql.org In-Reply-To: <1156448308.7223.71.camel@state.g2switchworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <78ED28FACE63744386D68D8A9D1CF5D4104ACF@MAIL.corp.lumeta.com> <1156285374.15743.118.camel@dogma.v10.wvs> <1156436690.15743.181.camel@dogma.v10.wvs> <1156448308.7223.71.camel@state.g2switchworks.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=3.816 tagged_above=0 required=5 tests=SPF_HELO_SOFTFAIL, SPF_SOFTFAIL X-Spam-Level: *** X-Archive-Number: 200608/396 X-Sequence-Number: 20581 On 8/24/06, Scott Marlowe wrote: > On Thu, 2006-08-24 at 13:57, Merlin Moncure wrote: > > On 8/24/06, Jeff Davis wrote: > > > On Thu, 2006-08-24 at 09:21 -0400, Merlin Moncure wrote: > > > > On 8/22/06, Jeff Davis wrote: > > > > > On Tue, 2006-08-22 at 17:56 -0400, Bucky Jordan wrote: > > > > it's not the parity, it's the seeking. Raid 5 gives you great > > > > sequential i/o but random is often not much better than a single > > > > drive. Actually it's the '1' in raid 10 that plays the biggest role > > > > in optimizing seeks on an ideal raid controller. Calculating parity > > > > was boring 20 years ago as it inolves one of the fastest operations in > > > > computing, namely xor. :) > > > > > > Here's the explanation I got: If you do a write on RAID 5 to something > > > that is not in the RAID controllers cache, it needs to do a read first > > > in order to properly recalculate the parity for the write. > > > > it's worse than that. if you need to read something that is not in > > the o/s cache, all the disks except for one need to be sent to a > > physical location in order to get the data. > > Ummmm. No. Not in my experience. If you need to read something that's > significantly larger than your stripe size, then yes, you'd need to do > that. With typical RAID 5 stripe sizes of 64k to 256k, you could read 8 > to 32 PostgreSQL 8k blocks from a single disk before having to move the > heads on the next disk to get the next part of data. A RAID 5, being > read, acts much like a RAID 0 with n-1 disks. i just don't see raid 5 benchmarks backing that up. i know how it is supposed to work on paper, but all of the raid 5 systems I work with deliver lousy seek performance. here is an example from the mysql folks: http://peter-zaitsev.livejournal.com/14415.html and another: http://storageadvisors.adaptec.com/2005/10/13/raid-5-pining-for-the-fjords/ also, with raid 5 you are squeezed on both ends, too few disks and you have an efficiency problem. too many disks and you start to get concerned about mtbf and raid rebuild times. > It's the writes that kill performance, since you've got to read two > disks and write two disks for every write, at a minimum. This is why > small RAID 5 arrays bottleneck so quickly. a 4 disk RAID 4 with two > writing threads is likely already starting to thrash. > > Or did you mean something else by that? well, that's correct, my point was that a 4 disk raid 1 can deliver more seeks, not necessarily that it is better. as you say writes would kill performance. raid 10 seems to be a good compromise. so is raid 6 possibly, although i dont see a lot performance data on that. merlin