pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Robin Iddon <robin@edesix.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: New system recommendations
Date: Thu, 27 Apr 2006 14:05:27 -0500
Message-ID: <1146164727.23538.322.camel@state.g2switchworks.com> (raw)
In-Reply-To: <445110EA.9050703@edesix.com>
References: <8511B4970E0D124898E973DF496F9B432515CF@stash.stackdump.local>
	<1146160194.23538.313.camel@state.g2switchworks.com>
	<445110EA.9050703@edesix.com>

On Thu, 2006-04-27 at 13:43, Robin Iddon wrote:
> > Anytime you're looking at a high write load on a database (not just
> > PostgreSQL) you should be looking at a hardware RAID controller with
> > battery backed cache and RAID 1 or RAID 1+0.
> >   
> We recently benchmarked the latest and greatest PCI-X SATA mega raid 
> controller (with NCQ support, so approaching SCSI performance) and we 
> found it was no faster than running s/w RAID-1 on a dual-core P4 with 
> the 2.6 series kernel.  It would no doubt offer an advantage on running 
> RAID-5 or any other RAID scheme that required XOR computation, but we 
> don't want to use RAID-5.
>
> However we did not fit the Transportable Battery Backup Unit and so we 
> didn't measure the benefit of early commit to the cache (fsync() returns 
> early, data is written to disk later, battery keeps data safe in the 
> meanwhile). 

That battery backed cache makes all the difference.  Also, unless
someone's done some work on it, the older linux kernel raid modules
serialized the access via multi-level RAID in such a way that RAID 1+0
was no faster than RAID 1.  You're right about RAID5 sw versus hw. 
Without the BBCache unit, they're pretty much the same, and generally
limited by the speed of the drives, not the method of implementation.

Note that the Areca controllers and a few others get much better
scores.  But, the megaraid and adaptec controllers are the only ones
dell includes in their boxen, so if it's a choice between the adaptec
and the megaraid, I'd normally pick the megaraid.  Note that some folks
have mentioned that Dell uses their own firmware on these cards, and
that firmware is supposedly slower than the stock firmware those cards
come with.

> I plan on repeating the experiment again later on in May once we have a 
> TBBU and will post the results here if anyone is interested.

I'd love to see how the newer cards perform.  I know that for RAID 1,
straight up, linux kernel sw RAID is quite speedy.  I'd imagine it would
take a fairly heavily written environment to see an advantage for the HW
controller.



view thread (15+ messages)  latest in thread

Message-ID: <1146164727.23538.322.camel@state.g2switchworks.com>
Permalink:  ../1146164727.23538.322.camel@state.g2switchworks.com/
Also on:    postgresql.org/message-id/1146164727.23538.322.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 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-admin@postgresql.org
  Cc: smarlowe@g2switchworks.com, robin@edesix.com
  Subject: Re: New system recommendations
  In-Reply-To: <1146164727.23538.322.camel@state.g2switchworks.com>
  References: <8511B4970E0D124898E973DF496F9B432515CF@stash.stackdump.local> <1146160194.23538.313.camel@state.g2switchworks.com> <445110EA.9050703@edesix.com> <1146164727.23538.322.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