From: Dave Chinner <david@fromorbit.com>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: Jesse Stroik <jstroik@ssec.wisc.edu>, xfs@oss.sgi.com
Subject: Re: Improving XFS file system inode performance
Date: Wed, 24 Nov 2010 07:39:06 +1100 [thread overview]
Message-ID: <20101123203906.GV22876@dastard> (raw)
In-Reply-To: <201011232127.37796@zmi.at>
On Tue, Nov 23, 2010 at 09:27:36PM +0100, Michael Monnerie wrote:
> On Dienstag, 23. November 2010 Jesse Stroik wrote:
> > As this file system is likely to continue to increase in number of
> > files at a fairly rapid rate, we're going to need a long term
> > strategy. I suspect it may be necessary in the near future to
> > double or quadruple the memory to 32GB or 64GB, but the uncertainty
> > in the formula makes me nervous.
>
> Using tools like "munin" helps you see the problem in graphs, so you can
> easily check what's going on. Munin draws graphs from a lot of
> parameters of a system, and helped me find problems that you couldn't
> find otherwise.
For XFS specific stats, PCP is your friend. It knows all about the
stats in /proc/fs/xfs/stats as well as most system level stats that
other toolѕ also collect and display...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-11-23 20:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 21:59 Improving XFS file system inode performance Jesse Stroik
2010-11-22 22:25 ` Emmanuel Florac
2010-11-22 22:32 ` Jesse Stroik
2010-11-22 23:44 ` Dave Chinner
2010-11-23 14:49 ` Jesse Stroik
2010-11-23 20:27 ` Dave Chinner
2010-11-23 20:27 ` Michael Monnerie
2010-11-23 20:39 ` Dave Chinner [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=20101123203906.GV22876@dastard \
--to=david@fromorbit.com \
--cc=jstroik@ssec.wisc.edu \
--cc=michael.monnerie@is.it-management.at \
--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