From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Jesse Stroik <jstroik@ssec.wisc.edu>
Subject: Re: Improving XFS file system inode performance
Date: Tue, 23 Nov 2010 21:27:36 +0100 [thread overview]
Message-ID: <201011232127.37796@zmi.at> (raw)
In-Reply-To: <4CEBD47F.1040004@ssec.wisc.edu>
[-- Attachment #1.1: Type: Text/Plain, Size: 928 bytes --]
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.
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531
// ****** Radiointerview zum Thema Spam ******
// http://www.it-podcast.at/archiv.html#podcast-100716
//
// Haus zu verkaufen: http://zmi.at/langegg/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-11-23 20:26 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 [this message]
2010-11-23 20:39 ` Dave Chinner
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=201011232127.37796@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=jstroik@ssec.wisc.edu \
--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