From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Alex Turner <armtuk@gmail.com>
Cc: Greg Smith <gsmith@gregsmith.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Bad iostat numbers
Date: Mon, 04 Dec 2006 10:37:34 -0600
Message-ID: <1165250254.14565.333.camel@state.g2switchworks.com> (raw)
In-Reply-To: <1165249513.14565.329.camel@state.g2switchworks.com>
References: <PEEPKDFEHHEMKBBFPOOKKEHCDKAA.carlos.reimer@opendb.com.br>
<Pine.GSO.4.64.0612032336250.19679@westnet.com>
<33c6269f0612032317t9f0bc77n3ff791a5cd88fc80@mail.gmail.com>
<1165249513.14565.329.camel@state.g2switchworks.com>
On Mon, 2006-12-04 at 10:25, Scott Marlowe wrote:
>
> OTOH, with the choice at my last place of employment being LSI or
> Adaptec, LSI was a much better choice. :)
>
> I'd ask which LSI megaraid you've tested, and what driver was used.
> Does RHEL4 have the megaraid 2 driver?
Just wanted to add that what we used our database for at my last company
was for lots of mostly small writes / reads. I.e. sequential throughput
didn't really matter, but random write speed did. for that application,
the LSI Megaraid with battery backed cache was great.
Last point, bonnie++ is a good benchmarking tool, but until you test
your app / postgresql on top of the hardware, you can't really say how
well it will perform.
A controller that looks fast under a single bonnie++ thread might
perform poorly when there are 100+ pending writes, and vice versa, a
controller that looks mediocre under bonnie++ might shine when there's
heavy parallel write load to handle.
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, armtuk@gmail.com, gsmith@gregsmith.com
Subject: Re: Bad iostat numbers
In-Reply-To: <1165250254.14565.333.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