pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: Madison Kelly <linux@alteeve.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Hardware purchase question
Date: 03 Jan 2005 15:36:07 -0500
Message-ID: <87wtuu6yiw.fsf@stark.xeocode.com> (raw)
In-Reply-To: <41D99E7E.3080704@alteeve.com>
References: <6.0.1.1.0.20041124114556.04b7cc80@mail.marketingsolutionsinc.com>
	<x77jnmb1jo.fsf@yertle.int.kciLink.com>
	<41BDD001.8070701@commandprompt.com>
	<330532b6050103112034cf47c8@mail.gmail.com>
	<41D99E7E.3080704@alteeve.com>


Madison Kelly <linux@alteeve.com> writes:

> Without it, specially in a failure state, the performance can collapse as
> the CPU performs all that extra math.

It's really not the math that makes raid 5 hurt. It's that in order to
calculate the checksum block the raid controller needs to read in the existing
checksum block and write out the new version. So every write causes not just
one drive seeking and writing, but a second drive seeking and performing a
read and a write.

The usual strategy for dealing with that is stuffing a huge nonvolatile cache
in the controller so those reads are mostly cached and the extra writes don't
saturate the i/o throughput. But those kinds of controllers are expensive and
not an option for software raid.

-- 
greg




view thread (12+ messages)  latest in thread

Message-ID: <87wtuu6yiw.fsf@stark.xeocode.com>
Permalink:  ../87wtuu6yiw.fsf@stark.xeocode.com/
Also on:    postgresql.org/message-id/87wtuu6yiw.fsf@stark.xeocode.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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: gsstark@mit.edu, linux@alteeve.com
  Subject: Re: Hardware purchase question
  In-Reply-To: <87wtuu6yiw.fsf@stark.xeocode.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