From: David Chinner <dgc@sgi.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: xfs@oss.sgi.com
Subject: Re: Proper swidth and sunit for RAID 5 (does it matter)?
Date: Wed, 16 Jan 2008 08:34:10 +1100 [thread overview]
Message-ID: <20080115213410.GM155407@sgi.com> (raw)
In-Reply-To: <alpine.DEB.0.999999.0801151227001.25921@p34.internal.lan>
On Tue, Jan 15, 2008 at 12:29:14PM -0500, Justin Piszcz wrote:
> Dave,
>
> What is the proper sunit and swidth for a 64, 256, and 1024 kilobyte chunk
> size with a 10-disk raid 5?
>
> Also, in the majority of benchmarks it does not seem to matter whether the
> FS is stripe-aligned or not (with SW raid)- does it mainly/only affect HW
> raid?
Affects both. If you are doing large I/O, both SW and HW raid will
avoid RMW cycles if you can do full stripe writes and that means
they go faster. The faster the RAID array, the bigger the difference
it will make.
If your tests are with small I/O or with a config that can't
do I/O large enough for full stripe writes, then you won't see
any difference as you're not avoiding RMW cycles.
> Current settings (10 disks):
>
> # xfs_info /dev/md3
> meta-data=/dev/md3 isize=256 agcount=4, agsize=82417536
Why 4 ags?
The low number of AGs is an optimisation for single disks,
not multi-disk arrays that have much more parallelism and
seek capacity available.
> blks
> = sectsz=4096 attr=2
> data = bsize=4096 blocks=329670144, imaxpct=25
> = sunit=0 swidth=0 blks, unwritten=1
And you don't even have su/sw set here, so XFS won't be doing
any alignment optimisation at all.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
prev parent reply other threads:[~2008-01-15 21:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 17:29 Proper swidth and sunit for RAID 5 (does it matter)? Justin Piszcz
2008-01-15 21:34 ` 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=20080115213410.GM155407@sgi.com \
--to=dgc@sgi.com \
--cc=jpiszcz@lucidpixels.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox