pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: Mario Splivalo <mario.splivalo@mobart.hr>
Cc: pgsql-admin@postgresql.org
Subject: Re: Server Hardware Configuration
Date: Mon, 21 Nov 2005 10:59:24 -0600
Message-ID: <20051121165924.GT19279@pervasive.com> (raw)
In-Reply-To: <1132565676.8689.9.camel@ekim>
References: <E8FEC853EDA289B924D8F213@betelgeuse.cct.rpi.edu>
	<20051120175337.GP19279@pervasive.com>
	<1132565676.8689.9.camel@ekim>

On Mon, Nov 21, 2005 at 10:34:36AM +0100, Mario Splivalo wrote:
> > RAID5 generally doesn't make for a fast database. The problem is that
> > there is a huge amount of overhead everytime you go to write something
> > out to a RAID5 array. With careful tuning of the background writer you
> > might be able to avoid some of that penalty, though your read
> > performance will likely still be affected by the write overhead.
> 
> RAID5 was not ment to improve performance, but to minimize disaster and
> downtime when your hard disk dies. We're using RAID5 with postgres. In
> the last 3 years we changed 5 disks, but the system downtime was zero
> minutes.

And the same would have been true with RAID10. In fact, RAID10 is more
reliable than RAID5; depending on what drives fail it's possible to lose
up to half of a RAID10 array without any data loss. If you ever lose
more than 2 drives at once with RAID5, your data is gone.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (16+ messages)  latest in thread

Message-ID: <20051121165924.GT19279@pervasive.com>
Permalink:  ../20051121165924.GT19279@pervasive.com/
Also on:    postgresql.org/message-id/20051121165924.GT19279@pervasive.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: jnasby@pervasive.com, mario.splivalo@mobart.hr
  Subject: Re: Server Hardware Configuration
  In-Reply-To: <20051121165924.GT19279@pervasive.com>
  References: <E8FEC853EDA289B924D8F213@betelgeuse.cct.rpi.edu> <20051120175337.GP19279@pervasive.com> <1132565676.8689.9.camel@ekim> <20051121165924.GT19279@pervasive.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