All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
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: Fri, 15 Jun 2007 15:33:43 -0500	[thread overview]
Message-ID: <4672F7A7.9040904@sandeen.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0706151634130.26033@p34.internal.lan>

Justin Piszcz wrote:
> Hi,
> 
> I was wondering if the XFS folks can recommend any optimizations for high 
> speed disk arrays using RAID5?
> 
> As well as if there is anything else I can do on the MD side?
> 
> fs.xfs.restrict_chown = 1
> fs.xfs.irix_sgid_inherit = 0
> fs.xfs.irix_symlink_mode = 0

OT but...

/me wonders if some of these could go away by now... :)

-Eric

> fs.xfs.panic_mask = 0
> fs.xfs.error_level = 3
> fs.xfs.xfssyncd_centisecs = 3000
> fs.xfs.inherit_sync = 1
> fs.xfs.inherit_nodump = 1
> fs.xfs.inherit_noatime = 1
> fs.xfs.xfsbufd_centisecs = 100
> fs.xfs.age_buffer_centisecs = 1500
> fs.xfs.inherit_nosymlinks = 0
> fs.xfs.rotorstep = 1
> fs.xfs.inherit_nodefrag = 1
> fs.xfs.stats_clear = 0
> 
> There is also vm/dirty tunable in /proc.
> 
> 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
> 
> 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
> 
> Justin.
> 
> 


  reply	other threads:[~2007-06-15 20:33 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 [this message]
2007-06-18  0:05 ` David Chinner
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=4672F7A7.9040904@sandeen.net \
    --to=sandeen@sandeen.net \
    --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.