From: Brad Langhorst <brad@langhorst.com>
To: xfs@oss.sgi.com
Subject: raid 10 su, sw settings
Date: Sun, 30 Dec 2007 19:00:39 -0500 [thread overview]
Message-ID: <1199059239.13944.65.camel@up> (raw)
I have this system
- 3ware 9650 controller
- 4 disk raid 10
- 64k stripe size
- this is a vmware host, so lots of r/w on a few big files.
I'm not entirely satisfied with its performance.
Typical blocks/sec from iostat during large file movements is about
100M/s read and 80M/s write.
When I set this up, I did not fully understand all the details... so I
want to check a few things.
- is the partition aligned correctly? i fear not...
/dev/sda1 * 1 24 192748+ 83 Linux
/dev/sda2 25 19449 156031312+ 83 Linux
Is this where I'm losing performance?
- What should the sunit and swidth settings be during mount?
I guess with raid 10 the width is 2 so...
sunit = 128 (64k/512) and swidth = 256 (2*64k/512)
Or maybe I should use width 1 ?
Remounting (mount -o remount) with these options does not lead
to a noticeable change in performance. Must I recreate the fs or
unmount and remount?
Here's the output of xfsinfo in case it's relevant.
xfs_info /
meta-data=/dev/sda2 isize=256 agcount=16, agsize=2437989
blks
= sectsz=512 attr=0
data = bsize=4096 blocks=39007824,
imaxpct=25
= sunit=0 swidth=0 blks, unwritten=1
naming =version 2 bsize=4096
log =internal bsize=4096 blocks=19046, version=1
= sectsz=512 sunit=0 blks
realtime =none extsz=65536 blocks=0, rtextents=0
next reply other threads:[~2007-12-31 16:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-31 0:00 Brad Langhorst [this message]
2007-12-31 17:04 ` raid 10 su, sw settings Justin Piszcz
2007-12-31 18:43 ` Brad Langhorst
2007-12-31 19:07 ` Justin Piszcz
2007-12-31 20:17 ` Iustin Pop
2007-12-31 20:55 ` Brad Langhorst
2007-12-31 21:42 ` Iustin Pop
2007-12-31 22:54 ` Brad Langhorst
2008-01-01 0:15 ` Iustin Pop
2007-12-31 18:53 ` pg_mh, Peter Grandi
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=1199059239.13944.65.camel@up \
--to=brad@langhorst.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.