From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: Calculating swidth On A RAID6 Volume
Date: Tue, 20 Jul 2010 15:22:39 +0200 [thread overview]
Message-ID: <201007201522.39455@zmi.at> (raw)
In-Reply-To: <3C5E029826A0704DB5998577FCFF46F0094DA1AD69@dagobah>
[-- Attachment #1.1: Type: Text/Plain, Size: 1898 bytes --]
On Dienstag, 20. Juli 2010 Andrew Debenham wrote:
> I'm am new to XFS and am in the process of trying to tune an XFS file
> system. I spent some time searching through this mailing list's
> archives but wasn't able to find anything that matched the question
> that I have (I apologize in advance if this issue has already been
> addressed).
Thanks for reminding me, wanted to write a FAQ entry, done now:
http://xfs.org/index.php/XFS_FAQ#Q:_How_to_calculate_the_correct_sunit.2Cswidth_values_for_optimal_performance
> I have a 3ware 9650SE-12M installed and have a RAID6 unit with 11 x
> 1.82 TB SATA drives and stripe size of 256KB. I found an earlier
> thread that discussed calculating the values for sunit and swidth
> for RAID5, which stated that the swidth would be "sunit x (# disks
> in stripe - 1)". So, finally the question - would the swidth for a
> RAID6 volume be "sunit x (# disks in stripe -2)?
>
> If that is the case, then here is what I would expect my values to
> be: sunit = 512
> swidth = 4608
I think sunit should be as big as the RAID controllers stripe size, as
it describes the smallest I/O XFS should do. So sunit=512 would make it
possible that XFS writes a single sector, while the RAID controller
needs to read/write 256KB with your stripe size, resulting in
performance degradation. But I'm no XFS dev, so maybe wait for a
clearing from someone who has deeper XFS knowledge than me.
sunit=262144
swidth=9
Would be my suggestion for your setup.
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31
****** Aktuelles Radiointerview! ******
http://www.it-podcast.at/aktuelle-sendung.html
// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-07-20 13:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 12:06 Calculating swidth On A RAID6 Volume Andrew Debenham
2010-07-20 12:40 ` Michael Weissenbacher
2010-07-20 13:22 ` Michael Monnerie [this message]
2010-07-20 14:13 ` Michael Weissenbacher
2010-07-20 14:44 ` Emmanuel Florac
2010-07-20 15:00 ` Michael Monnerie
2010-07-20 15:27 ` Emmanuel Florac
2010-07-21 6:54 ` Dave Chinner
2010-07-20 15:04 ` Michael Monnerie
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=201007201522.39455@zmi.at \
--to=michael.monnerie@is.it-management.at \
--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