From: David Chinner <dgc@sgi.com>
To: Sebastian Brings <sebas@silexmedia.com>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
Robert Petkus <rpetkus@bnl.gov>,
xfs@oss.sgi.com
Subject: Re: Poor performance -- poor config?
Date: Fri, 22 Jun 2007 09:59:32 +1000 [thread overview]
Message-ID: <20070621235932.GZ85884050@sgi.com> (raw)
In-Reply-To: <55EF1E5D5804A542A6CA37E446DDC206F5C5AA@mapibe17.exchange.xchg>
On Thu, Jun 21, 2007 at 08:37:36AM +0200, Sebastian Brings wrote:
> Not sure if it makes much sense to set stripe unit and width for a Raid
> which appears as a single device.
Certainly it does.
That way you get stripe aligned allocation and therfore you are
much more likely to get full-stripe width writes instead of unaligned
writes that force RMW cycles on the RAID controller for parity calculations.
> As you state, the "width" of your DS lun is 4 x 512K == 2MB. In case you
> don't have write cache enabled each of your 1MB writes will cause the DS
> to write to two out of four disks only, causing heavy overhead to create
> parity.
You're assuming stripe aligned I/O there. That 1MB could hit 3 of the 4
data disks - if you don't have a stripe unit set then that will
be the common case. i.e. its worse than you think :/
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
prev parent reply other threads:[~2007-06-25 5:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 20:59 Poor performance -- poor config? Robert Petkus
2007-06-20 21:04 ` Justin Piszcz
2007-06-20 21:16 ` Robert Petkus
2007-06-20 21:23 ` Justin Piszcz
2007-06-21 6:37 ` Sebastian Brings
2007-06-21 23:59 ` David Chinner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070621235932.GZ85884050@sgi.com \
--to=dgc@sgi.com \
--cc=jpiszcz@lucidpixels.com \
--cc=rpetkus@bnl.gov \
--cc=sebas@silexmedia.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.