From: Jesse Stroik <jstroik@ssec.wisc.edu>
To: Dave Chinner <david@fromorbit.com>
Cc: Linux XFS <xfs@oss.sgi.com>
Subject: Re: Improving XFS file system inode performance
Date: Tue, 23 Nov 2010 08:49:35 -0600 [thread overview]
Message-ID: <4CEBD47F.1040004@ssec.wisc.edu> (raw)
In-Reply-To: <20101122234419.GK13830@dastard>
Dave,
Thanks. This is precisely what I was looking for. I'll let you know
how it turns out.
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.
For a situation like this, it would be ideal if we could specify an
inode cache size.
Thanks,
Jesse
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-11-23 14:47 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 [this message]
2010-11-23 20:27 ` Dave Chinner
2010-11-23 20:27 ` Michael Monnerie
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=4CEBD47F.1040004@ssec.wisc.edu \
--to=jstroik@ssec.wisc.edu \
--cc=david@fromorbit.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