pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Michael Stone <mstone+postgres@mathom.us>
Cc: Jim C. Nasby <jnasby@pervasive.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Slow restoration question
Date: Wed, 03 May 2006 14:40:15 -0500
Message-ID: <1146685215.22037.46.camel@state.g2switchworks.com> (raw)
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>

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.



view thread (23+ messages)  latest in thread

Message-ID: <1146685215.22037.46.camel@state.g2switchworks.com>
Permalink:  ../1146685215.22037.46.camel@state.g2switchworks.com/
Also on:    postgresql.org/message-id/1146685215.22037.46.camel@state.g2switchworks.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: smarlowe@g2switchworks.com, mstone+postgres@mathom.us, jnasby@pervasive.com
  Subject: Re: Slow restoration question
  In-Reply-To: <1146685215.22037.46.camel@state.g2switchworks.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox