From: Chris Browne <cbbrowne@acm.org>
To: pgsql-performance@postgresql.org
Subject: Re: Advice on RAID card
Date: Sun, 25 Sep 2005 20:10:00 -0400
Message-ID: <60ek7cn0yv.fsf@dba2.int.libertyrms.com> (raw)
References: <IGEGINLEEDLANNHAAKCMOECJCCAA.gaulakh@ecmarket.com>
<op.sxll3du6th1vuj@localhost>
<43367937.40809@canaan.co.il>
<ABE6B997-2C1E-43B1-9F18-28F54B1620FE@fastcrypt.com>
<4336C57B.6090800@commandprompt.com>
<op.sxn1sdofth1vuj@localhost>
<4336CEAA.7070208@commandprompt.com>
jd@commandprompt.com ("Joshua D. Drake") writes:
> There is a huge advantage to software raid on all kinds of
> levels. If you have the CPU then I suggest it. However you will
> never get the performance out of software raid on the high level
> (think 1 gig of cache) that you would on a software raid setup.
This appears to be a case where the "ludicrous MHz increases" on
desktop CPUs has actually provided a material benefit.
The sorts of embedded controllers typically used on RAID controllers
are StrongARMs and i960s, and, well, 250MHz is actually fast for
these.
When AMD and Intel fight over adding gigahertz and megabytes of cache
to their chips, this means that the RAID work can get pushed over to
one's "main CPU" without chewing up terribly much of its bandwidth.
That says to me that in the absence of battery backed cache, it's not
worth having a "bottom-end" RAID controller. Particularly if the
death of the controller would be likely to kill your data.
Battery-backed cache changes the value proposition, of course...
--
select 'cbbrowne' || '@' || 'acm.org';
http://cbbrowne.com/info/linuxdistributions.html
All generalizations are false, including this one.
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: cbbrowne@acm.org
Subject: Re: Advice on RAID card
In-Reply-To: <60ek7cn0yv.fsf@dba2.int.libertyrms.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