Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 5318C64FD68 for ; Wed, 20 Aug 2008 12:03:16 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 84996-03-6 for ; Wed, 20 Aug 2008 12:03:12 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by postgresql.org (Postfix) with ESMTP id 9363465014C for ; Wed, 20 Aug 2008 12:02:57 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id 29so747654ugo.7 for ; Wed, 20 Aug 2008 08:02:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=vAOEF8+3gJBkV5AgJQXACpcf1DAxsbEJpuLR2x3yCp0=; b=gEgvGOvbhgMvqdCA3Oz+Ugq4rJRL38ZWdZ5IhRBgD4Vb0bQs7UEqCbYxatiR1+VLR5 euYbK+pMs5238DdjiDwovXv876+6+/bnAu4YoNtwReQU/Txlv4kIavZ8WOABNGgV6uW5 uur65VhOiDRYINh1i7lCl8rpiY2pVPOO4oQvs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=Ni25gdxho0ON73ofK0OL9dbRlncSgsHIGQOspONy9HkR6baii1Hk3+FtrVUmeHUexE jPc5toGYq56eptT/2HiTNR4QkLdqoPmqT/NTDcgofPSPPhg0r9AX6oZzETNH7giF3W3+ aMMyftMot6CNDhk/VoZ/4AR1KTqAFG64VLRoM= Received: by 10.210.58.13 with SMTP id g13mr220768eba.54.1219244576231; Wed, 20 Aug 2008 08:02:56 -0700 (PDT) Received: by 10.210.34.14 with HTTP; Wed, 20 Aug 2008 08:02:56 -0700 (PDT) Message-ID: <70c01d1d0808200802w5f10fd05i93189c530aa41457@mail.gmail.com> Date: Wed, 20 Aug 2008 08:02:56 -0700 From: "Mark Wong" To: david@lang.hm Subject: Re: Software vs. Hardware RAID Data Cc: "pgsql-performance@postgresql.org" , "Gabrielle Roth" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <70c01d1d0808192223h10b4f018w56357ba68621bc98@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200808/219 X-Sequence-Number: 31100 On Tue, Aug 19, 2008 at 10:49 PM, wrote: > On Tue, 19 Aug 2008, Mark Wong wrote: > >> Hi all, >> >> We started an attempt to slice the data we've been collecting in >> another way, to show the results of software vs. hardware RAID: >> >> >> http://wiki.postgresql.org/wiki/HP_ProLiant_DL380_G5_Tuning_Guide#Hardware_vs._Software_Raid >> >> The angle we're trying to show here is the processor utilization and >> i/o throughput for a given file system and raid configuration. I >> wasn't sure about the best way to present it, so this is how it looks >> so far. Click on the results for a chart of the aggregate processor >> utilization for the test. >> >> Comments, suggestions, criticisms, et al. welcome. > > it's really good to show cpu utilization as well as throughput, but how > about showing the cpu utilization as %cpu per MB/s (possibly with a flag to > indicate any entries that look like they may have hit cpu limits) Ok, we'll add that and see how it looks. > why did you use 4M stripe size on the software raid? especially on raid 5 > this seems like a lot of data to have to touch when making an update. I'm sort of taking a shotgun approach, but ultimately we hope to show whether there is significant impact of the stripe width relative to the database blocksize. Regards, Mark