pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mark Wong <markwkm@gmail.com>
To: david@lang.hm
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Cc: Gabrielle Roth <gorthx@gmail.com>
Subject: Re: Software vs. Hardware RAID Data
Date: Wed, 20 Aug 2008 08:02:56 -0700
Message-ID: <70c01d1d0808200802w5f10fd05i93189c530aa41457@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0808192244380.12859@asgard.lang.hm>
References: <70c01d1d0808192223h10b4f018w56357ba68621bc98@mail.gmail.com>
	<alpine.DEB.1.10.0808192244380.12859@asgard.lang.hm>

On Tue, Aug 19, 2008 at 10:49 PM,  <david@lang.hm> 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



view thread (5+ messages)  latest in thread

Message-ID: <70c01d1d0808200802w5f10fd05i93189c530aa41457@mail.gmail.com>
Permalink:  ../70c01d1d0808200802w5f10fd05i93189c530aa41457@mail.gmail.com/
Also on:    postgresql.org/message-id/70c01d1d0808200802w5f10fd05i93189c530aa41457@mail.gmail.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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: markwkm@gmail.com, david@lang.hm, gorthx@gmail.com
  Subject: Re: Software vs. Hardware RAID Data
  In-Reply-To: <70c01d1d0808200802w5f10fd05i93189c530aa41457@mail.gmail.com>
  References: <70c01d1d0808192223h10b4f018w56357ba68621bc98@mail.gmail.com> <alpine.DEB.1.10.0808192244380.12859@asgard.lang.hm> <70c01d1d0808200802w5f10fd05i93189c530aa41457@mail.gmail.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