From: Mark Lewis <mark.lewis@mir3.com>
To: Merlin Moncure <mmoncure@gmail.com>
Cc: Jeff Davis <pgsql@j-davis.com>
Cc: Bucky Jordan <bjordan@lumeta.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: PowerEdge 2950 questions
Date: Thu, 24 Aug 2006 12:28:42 -0700
Message-ID: <1156447722.9657.255.camel@archimedes> (raw)
In-Reply-To: <b42b73150608241157j7076d268h42a57cf3c26a4b34@mail.gmail.com>
References: <78ED28FACE63744386D68D8A9D1CF5D4104ACF@MAIL.corp.lumeta.com>
<1156285374.15743.118.camel@dogma.v10.wvs>
<b42b73150608240621v453e3aeen44f09cd274f9a7@mail.gmail.com>
<1156436690.15743.181.camel@dogma.v10.wvs>
<b42b73150608241157j7076d268h42a57cf3c26a4b34@mail.gmail.com>
> it's worse than that. if you need to read something that is not in
> the o/s cache, all the disks except for one need to be sent to a
> physical location in order to get the data. Thats the basic rule with
> striping: it optimizes for sequential i/o in expense of random i/o.
> There are some optimizations that can help, but not much. caching by
> the controller can increase performance on writes because it can
> optimize the movement across the disks by instituting a delay between
> the write request and the actual write.
>
> raid 1 (or 1+x) is the opposite. It allows the drive heads to move
> independantly on reads when combined with some smart algorithms.
> writes however must involve all the disk heads however. Many
> controllers do not to seem to optimze raid 1 properly although linux
> software raid seems to.
>
> A 4 disk raid 1, for example, could deliver four times the seek
> performance which would make it feel much faster than a 4 disk raid 0
> under certain conditions.
I understand random mid-sized seeks (seek to x and read 512k) being slow
on RAID5, but if the read size is small enough not to cross a stripe
boundary, this could be optimized to only one seek on one drive. Do
most controllers just not do this, or is there some other reason that
I'm not thinking of that would force all disks to seek?
-- Mark
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: mark.lewis@mir3.com, mmoncure@gmail.com, pgsql@j-davis.com, bjordan@lumeta.com
Subject: Re: PowerEdge 2950 questions
In-Reply-To: <1156447722.9657.255.camel@archimedes>
* 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