From: Jesse Stroik <jstroik@ssec.wisc.edu>
To: Linux XFS <xfs@oss.sgi.com>
Subject: Improving XFS file system inode performance
Date: Mon, 22 Nov 2010 15:59:51 -0600 [thread overview]
Message-ID: <4CEAE7D7.6050401@ssec.wisc.edu> (raw)
XFS community,
I have a couple of medium-sized file systems on an ftp server (10TB file
system mounted within a 20TB file system). The load on these file
systems is getting pretty high because we have many users mirroring
datasets from the server. As far as I can tell, the main issue is with
inode performance. For example, an 'ls' on a directory may take 20
seconds to complete. At any given time, there is > 50 ftp STAT, LIST or
NLST commands some of which list entire directories or wildcards.
Sadly, the file system was created with 32 bit inodes. I've remounted
it with the inode64 option, but I assume performance will be boosted
primarily when old files are replaced with new files. Is there anything
I can do to improve performance now?
I'm also using noatime and logbufs=8.
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.
I'd also be interested in inode cache tuning options specific to XFS.
i've been having trouble finding documentation on this particular issue.
This is a production file system so please frame your suggestions with
respect to that. It is a RHEL 5.5 system running xfsprogs-2.9.4.1
centos and redhat kernel version 2.6.18-194.17.1 which includes a
variety of backported xfs fixes.
Best,
Jesse
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-11-22 21:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 21:59 Jesse Stroik [this message]
2010-11-22 22:25 ` Improving XFS file system inode performance 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
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=4CEAE7D7.6050401@ssec.wisc.edu \
--to=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