From: Chris Wedgwood <cw@f00f.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: xfs@oss.sgi.com
Subject: Re: Anyone using XFS in production on > 20TiB volumes?
Date: Wed, 22 Dec 2010 09:32:09 -0800 [thread overview]
Message-ID: <20101222173209.GA29291@puku.stupidest.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1012221209150.5245@p34.internal.lan>
On Wed, Dec 22, 2010 at 12:10:06PM -0500, Justin Piszcz wrote:
> Do you have an example/of what you found?
i don't have the numbers anymore, they are with a previous employer.
basically using dbench (there were cifs NAS machines, so dbench seemed
as good or bad as anything to test with) the performance was about 3x
better between 'old' and 'new' with a small number of workers and
about 10x better with a large number
i don't know how much difference each of inode64 and getting the geom
right made each, but bother were quite measurable in the graphs i made
at the time
from memory the machines are raid50 (4x (5+1)) with 2TB drives, so
about 38TB usable on each one
initially these machines were 3ware controllers and later on LSI (the
two products lines have since merged so it's not clear how much
difference that makes now)
in testing 16GB for xfs_repair wasn't enough, so they were upped to
64GB, that's likely largely a result of the fact there were 100s of
millions of small files (as well as some large ones)
> Is it dependent on the RAID card?
perhaps, do you have a BBU and enable WC? certainly we found the LSI
cards to be faster in most cases than the (now old) 3ware
where i am now i use larger chassis and no hw raid cards, using sw
raid on these works spectacularly well with the exception of burst of
small seeky writes (which a BBU + wc soaks up quite well)
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-12-22 17:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 16:30 Anyone using XFS in production on > 20TiB volumes? Justin Piszcz
2010-12-22 16:56 ` Emmanuel Florac
2010-12-22 19:03 ` Eric Sandeen
2010-12-23 0:26 ` Emmanuel Florac
2010-12-23 0:28 ` Justin Piszcz
2010-12-23 0:56 ` Dave Chinner
2010-12-23 9:43 ` Justin Piszcz
2010-12-23 12:03 ` Emmanuel Florac
2010-12-23 18:06 ` Justin Piszcz
2010-12-23 18:55 ` Emmanuel Florac
2010-12-23 19:07 ` Justin Piszcz
2010-12-23 19:54 ` Stan Hoeppner
2010-12-23 21:48 ` Emmanuel Florac
2010-12-23 23:21 ` Stan Hoeppner
2010-12-23 21:50 ` Emmanuel Florac
2010-12-23 22:04 ` Justin Piszcz
2010-12-23 19:29 ` Justin Piszcz
2010-12-23 19:58 ` Stan Hoeppner
2010-12-24 1:01 ` Stan Hoeppner
2010-12-23 21:12 ` Eric Sandeen
2010-12-23 1:10 ` Emmanuel Florac
2010-12-22 17:06 ` Chris Wedgwood
2010-12-22 17:10 ` Justin Piszcz
2010-12-22 17:32 ` Chris Wedgwood [this message]
2010-12-22 17:35 ` Justin Piszcz
2010-12-22 18:50 ` Chris Wedgwood
2010-12-22 19:24 ` Justin Piszcz
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=20101222173209.GA29291@puku.stupidest.org \
--to=cw@f00f.org \
--cc=jpiszcz@lucidpixels.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox