Re: Slow restoration question

From: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
To: Michael Stone <mstone+postgres(at)mathom(dot)us>
Cc: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Slow restoration question
Date: 2006-05-03 19:40:15
Message-ID: 1146685215.22037.46.camel@state.g2switchworks.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Michael Stone 2006-05-03 20:53:08 Re: Slow restoration question
Previous Message Michael Stone 2006-05-03 19:26:54 Re: Slow restoration question