From: Scott Marlowe <scott.marlowe@gmail.com>
To: Fernando Hevia <fhevia@ip-tel.com.ar>
Cc: cluster <skrald@amossen.dk>
Cc: pgsql-performance@postgresql.org
Subject: Re: Best hardware/cost tradoff?
Date: Thu, 28 Aug 2008 15:47:37 -0600
Message-ID: <dcc563d10808281447x764cc464gf984d9a22b2f454c@mail.gmail.com> (raw)
In-Reply-To: <064701c90949$51d117d0$8f01010a@iptel.com.ar>
References: <g96ttt$2l3m$1@news.hub.org>
<064701c90949$51d117d0$8f01010a@iptel.com.ar>
On Thu, Aug 28, 2008 at 2:04 PM, Fernando Hevia <fhevia@ip-tel.com.ar> wrote:
>
> I havent had any issues with software raid (mdadm) and hot-swaps. It keeps
> working in degraded mode and as soon as you replace the defective disk it
> can reconstruct the array on the fly. Performance will suffer while at it
> but the service keeps up.
I too put my vote behind mdadm for ease of use. However, there are
reports that certain levels of RAID in linux kernel RAID that are
supposed to NOT handle write barriers properly. So that's what
worries me.
> The battery backup makes a very strong point for a hw controller. Still, I
> have heard good things on combining a HW controller with JBODS leaving the
> RAID affair to mdadm. In your scenario though with "*lots* of random reads",
This is especially true on slower RAID controllers. A lot of RAID
controllers in the $300 range with battery backed caching don't do
RAID real well, but do caching ok. If you can't afford a $1200 RAID
card then this might be a good option.
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: scott.marlowe@gmail.com, fhevia@ip-tel.com.ar, skrald@amossen.dk
Subject: Re: Best hardware/cost tradoff?
In-Reply-To: <dcc563d10808281447x764cc464gf984d9a22b2f454c@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