public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Stroik <jstroik@ssec.wisc.edu>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: Linux XFS <xfs@oss.sgi.com>
Subject: Re: Improving XFS file system inode performance
Date: Mon, 22 Nov 2010 16:32:06 -0600	[thread overview]
Message-ID: <4CEAEF66.7030708@ssec.wisc.edu> (raw)
In-Reply-To: <20101122232528.21b78a9e@galadriel.home>

On 11/22/2010 04:25 PM, Emmanuel Florac wrote:
> Le Mon, 22 Nov 2010 15:59:51 -0600 vous écriviez:
>
>> Performance was fine before the file system was filled -- last week
>> ~8TB showed up and filled the 20TB file system.  Since, it has been
>> performing poorly.
>
> Maybe it got fragmented? How does fragmentation look like?


I wasn't able to resolve this in reasonable time.  Part of the issue is 
that we're dealing with files within about 100k directories.  I'll 
attempt to get the fragmentation numbers overnight.

I suspect the regularly listed set of files on this fs exceeds the inode 
cache.  Where can I determine the cache misses and tune the file system?

Best,
Jesse

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

  reply	other threads:[~2010-11-22 22:30 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 [this message]
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

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=4CEAEF66.7030708@ssec.wisc.edu \
    --to=jstroik@ssec.wisc.edu \
    --cc=eflorac@intellique.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