From: David Chinner <dgc@sgi.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: xfs@oss.sgi.com, linux-raid@vger.kernel.org
Subject: Re: XFS Tunables for High Speed Linux SW RAID5 Systems?
Date: Mon, 18 Jun 2007 10:05:02 +1000 [thread overview]
Message-ID: <20070618000502.GU86004887@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706151634130.26033@p34.internal.lan>
On Fri, Jun 15, 2007 at 04:36:07PM -0400, Justin Piszcz wrote:
> Hi,
>
> I was wondering if the XFS folks can recommend any optimizations for high
> speed disk arrays using RAID5?
[sysctls snipped]
None of those options will make much difference to performance.
mkfs parameters are the big ticket item here....
> There is also vm/dirty tunable in /proc.
That changes benchmark times by starting writeback earlier, but
doesn't affect actual writeback speed.
> I was wondering what are some things to tune for speed? I've already
> tuned the MD layer but is there anything with XFS I can also tune?
>
> echo "Setting read-ahead to 64MB for /dev/md3"
> blockdev --setra 65536 /dev/md3
Why so large? That's likely to cause readahead thrashing problems
under low memory....
> echo "Setting stripe_cache_size to 16MB for /dev/md3"
> echo 16384 > /sys/block/md3/md/stripe_cache_size
>
> (also set max_sectors_kb) to 128K (chunk size) and disable NCQ
Why do that? You want XFS to issue large I/Os and the block layer
to split them across all the disks. i.e. you are preventing full
stripe writes from occurring by doing that.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-06-18 0:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 20:36 XFS Tunables for High Speed Linux SW RAID5 Systems? Justin Piszcz
2007-06-15 20:33 ` Eric Sandeen
2007-06-18 0:05 ` David Chinner [this message]
2007-06-18 11:07 ` Justin Piszcz
2007-06-18 11:59 ` David Greaves
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=20070618000502.GU86004887@sgi.com \
--to=dgc@sgi.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-raid@vger.kernel.org \
--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.