public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs@oss.sgi.com
Subject: Re: Anyone using XFS in production on > 20TiB volumes?
Date: Thu, 23 Dec 2010 11:56:30 +1100	[thread overview]
Message-ID: <20101223005630.GJ4907@dastard> (raw)
In-Reply-To: <alpine.DEB.2.00.1012221928050.7452@p34.internal.lan>

On Wed, Dec 22, 2010 at 07:28:29PM -0500, Justin Piszcz wrote:
> 
> 
> On Thu, 23 Dec 2010, Emmanuel Florac wrote:
> 
> >Le Wed, 22 Dec 2010 13:03:13 -0600 vous écriviez:
> >
> >>http://xfs.org/index.php/XFS_FAQ#Q:_I_want_to_tune_my_XFS_filesystems_for_.3Csomething.3E
> >>
> >>which mentions getting your geometry right if it's hardware raid
> >>that can't be detected automatically.
> >
> >Just as a side note : I tried several times to manually set the
> >filesystem layout to precisely match the underlying hardware RAID
> >with sunit and swidth but didn't find that it made a noticeable
> >difference. On my 39.9 TB systems, the default agcount is 39, while the
> >optimum would be (theorically at least)  42.
> 
> Hi, I concur, for hardware raid (at least on 3ware cards) I have
> found it makes no difference, thanks for confirming.

I'd constrain that statement to "no difference for the workloads
and hardware tested".

Indeed, testing an empty filesystem will often show no difference in
performance, because typically problems don't show up until you've
started to age the filesystem significantly. When the filesystem has
started to age, the difference between having done lots of stripe
unit/width aligned allocation vs none can be very significant....

Hence don't assume that because you can't see any difference on a
brand new, empty filesystem there never will be a difference over
the life of the filesytem...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-12-23  0:54 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 [this message]
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
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=20101223005630.GJ4907@dastard \
    --to=david@fromorbit.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=sandeen@sandeen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox