From: "Alex Madarasz" <List@madalexlists.nospammail.net>
To: xfs@oss.sgi.com
Subject: Re: Fedora 8.0.1 XFS Tune on HW RAID for Max Write Throughput?
Date: Sun, 16 Dec 2007 20:17:44 -0500 [thread overview]
Message-ID: <1197854264.9694.1226902133@webmail.messagingengine.com> (raw)
In-Reply-To: <4764AB08.7040608@sandeen.net>
On Sat, 15 Dec 2007 22:35:20 -0600, "Eric Sandeen"
<sandeen@sandeen.net> said:
> Alex Madarasz wrote:
> > We're building a new Fedora 8.0.1 Linux system to stream data from a
> > 250Msps ADC to disk, and want to start tuning the system
> > configuration for maximum XFS write performance. To date, without
> > any significant effort at tuning our Fedora 7 dev system, we're
> > seeing 250MBps write with 8-bit samples and ~ 300MBps write with 16-
> > bit samples. We want to push the tuning as far as we can go with
> > this architecture before we start looking at other hardware options.
> > Looking at various other tuning pages on the Web finds few that are
> > interested in maxing out sequential writes to very large arrays
> > while using SAS HW RAID with big fast SAS drives too.
> ...
>
> > XFS Tuning Options?
> >
> > - HW RAID0:
> > - Array/logical disk HW RAID stripe size?
>
> At any rate you'll want to match xfs's geometry with the raid
> geometry.
The HP P400 stripe size defaults to 128K and can go up to 256K (and down
to 64K, 32K, ...). Any reason, with big sequential XFS write loads, I
shouldn't just max it out at 256K and move on?
I understand Linux XFS block size is limited to 4KiB max on Intel 32-bit
architectures ... including PAE?
> > - Cache enabled (some reports that cache s/b turned off?)?
>
> If it's battery-backed cache, leave it on, and disable barriers in xfs
> (it's a mount option)
It is indeed 512M of HP Battery-Backed Write Cache (BBWC).
> > - xfs mkfs / mount options?
>
> David mentioned these before as a generic place to start:
>
> # mkfs.xfs -f -l lazy-count=1,version=2,size=128m -i attr=2 -d
> # agcount=4
> <dev>
> # mount -o logbsize=256k <dev> <mtpt>
>
> and that those would be upcoming new defaults for mkfs.
>
> 4 ags may not be what you want for a ~2T filesystem.
> > - External Log?
> > - How big a partition on the E200i?
> > - mkfs / mount options?
>
> not sure if an external log would be beneficial or not.
prev parent reply other threads:[~2007-12-17 1:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 17:38 Fedora 8.0.1 XFS Tune on HW RAID for Max Write Throughput? Alex Madarasz
2007-12-16 4:35 ` Eric Sandeen
2007-12-16 9:07 ` Justin Piszcz
2007-12-16 23:31 ` David Chinner
2007-12-16 23:47 ` Justin Piszcz
2007-12-17 0:37 ` David Chinner
2007-12-21 5:07 ` Changliang Chen
2007-12-17 1:17 ` Alex Madarasz [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=1197854264.9694.1226902133@webmail.messagingengine.com \
--to=list@madalexlists.nospammail.net \
--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.