X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id C5EC59FA195 for ; Wed, 3 May 2006 16:40:28 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 62074-05 for ; Wed, 3 May 2006 16:40:17 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id 689219F9CC1 for ; Wed, 3 May 2006 16:40:16 -0300 (ADT) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Wed, 3 May 2006 19:40:15 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 03 May 2006 14:40:15 -0500 Subject: Re: Slow restoration question From: Scott Marlowe To: Michael Stone Cc: "Jim C. Nasby" , pgsql-performance@postgresql.org In-Reply-To: <20060503192652.GA16533@mathom.us> References: <1146595755.12053.111.camel@archimedes> <758B0591-3C9C-418B-9AF2-E962003C4904@rackspace.com> <20060502215329.GI97354@pervasive.com> <4A7F9950-65E0-4FA5-9FEC-BA1A93E615E5@clickspace.com> <20060503121847.GN31328@mathom.us> <30D5959B-3CCD-4CB4-B2D7-30DEA9F08BB6@torgo.978.org> <20060503155938.GO31328@mathom.us> <1146672434.22037.38.camel@state.g2switchworks.com> <20060503170604.GP31328@mathom.us> <20060503180821.GZ97354@pervasive.com> <20060503192652.GA16533@mathom.us> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1146685215.22037.46.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Wed, 03 May 2006 14:40:15 -0500 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/93 X-Sequence-Number: 18880 On Wed, 2006-05-03 at 14:26, Michael Stone wrote: > On Wed, May 03, 2006 at 01:08:21PM -0500, Jim C. Nasby wrote: > >Well, in this case the question was about random write access, which dd > >won't show you. > > That's the kind of thing you need to measure against your workload. Of course, the final benchmarking should be your application. But, supposed you're comparing 12 or so RAID controllers for a one week period, and you don't even have the app fully written yet, and because of time constraints, you'll need the server ready before the app is done. You don't need perfection, but you need some idea how the array performs. I maintain that both methodologies have their uses. Note that I'm referring to bonnie++ as was an earlier poster. It certainly seems capable of giving you a good idea of how your hardware will behave under load.