From: Richard Ems <richard.ems@cape-horn-eng.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: XFS unlink still slow on 3.1.9 kernel ?
Date: Tue, 14 Feb 2012 10:48:25 +0100 [thread overview]
Message-ID: <4F3A2DE9.5050901@cape-horn-eng.com> (raw)
In-Reply-To: <20120213211654.GA20192@infradead.org>
Hi Christoph, hi list,
I don;t have ONE dir with that 11 million files, it's one dir with many
directories and a total of about 11 million files AND dirs! See output
below!
On 02/13/2012 10:16 PM, Christoph Hellwig wrote:
> On Mon, Feb 13, 2012 at 07:48:58PM +0100, Richard Ems wrote:
>> I already updated to 3.2.4 and started the same "find dir" command again
>> that previously took 100 min to run. It has been running now for over 30
>> min ...
>>
>> Should this "find" run time also improve ?
>
> No, not by that change anyway.
It didn't improve, 100 min again.
>> Or will only unlink run time improve ?
>
> Yes.
rm took about 110 min.
>> Do I have to mount the XFS partition with some new/old/special option?
>
> I'd have to look into it in more detail. IIRC you said you're using
> RAID6 which can be fairly nasty for small reads. Did you use the
> inode64 mount option on the filesystem?
No, I did not use it, but I was thinking about and ran the script from
http://sandeen.net/misc/summarise_stat.pl and got as an example on /bin:
# /net/c3m/usr/local/software/XFS/summarise_stat.pl /bin/
9 6.2% are scripts (shell, perl, whatever)
65 44.8% don't use any stat() family calls at all
61 42.1% use 32-bit stat() family interfaces only
9 6.2% use 64-bit stat64() family interfaces only
1 0.7% use both 32-bit and 64-bit stat() family interfaces
So I was not sure if I should use inode64 or not.
This are the times that the run took yesterday:
Mon Feb 13 19:14:07 CET 2012
+ wc -l
+ find 2012-02-13/
11377443
real 101m30.811s
user 0m17.365s
sys 1m4.632s
Mon Feb 13 20:55:38 CET 2012
+ wc -l
+ find 2012-02-13/ -type d
834591
real 103m52.686s
user 0m11.765s
sys 1m41.018s
+ wc -l
+ find 2012-02-13/ -type f
10539154
real 104m38.421s
user 0m19.905s
sys 1m47.551s
+ /bin/rm -i -rf 2012-02-13/
real 110m55.764s
user 0m13.401s
sys 4m3.115s
Tue Feb 14 02:15:05 CET 2012
Thanks again,
Richard
--
Richard Ems mail: Richard.Ems@Cape-Horn-Eng.com
Cape Horn Engineering S.L.
C/ Dr. J.J. Dómine 1, 5º piso
46011 Valencia
Tel : +34 96 3242923 / Fax 924
http://www.cape-horn-eng.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-02-14 9:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 16:57 XFS unlink still slow on 3.1.9 kernel ? Richard Ems
2012-02-13 17:08 ` Christoph Hellwig
2012-02-13 17:11 ` Richard Ems
2012-02-13 17:15 ` Christoph Hellwig
2012-02-13 17:26 ` Richard Ems
2012-02-13 17:29 ` Christoph Hellwig
2012-02-13 17:53 ` Richard Ems
2012-02-13 18:02 ` Christoph Hellwig
2012-02-13 18:06 ` Richard Ems
2012-02-13 18:10 ` Christoph Hellwig
2012-02-13 18:18 ` Richard Ems
2012-02-13 18:48 ` Richard Ems
2012-02-13 21:16 ` Christoph Hellwig
2012-02-14 5:31 ` Stan Hoeppner
2012-02-14 9:48 ` Richard Ems [this message]
2012-02-14 19:43 ` Christoph Hellwig
2012-02-14 9:49 ` Richard Ems
2012-02-14 10:54 ` Richard Ems
2012-02-14 11:44 ` Richard Ems
2012-02-14 0:09 ` Dave Chinner
2012-02-14 12:32 ` Richard Ems
2012-02-14 19:45 ` Christoph Hellwig
2012-02-15 12:07 ` Richard Ems
2012-02-15 1:27 ` Dave Chinner
2012-02-15 12:07 ` Richard Ems
-- strict thread matches above, loose matches on Subject: below --
2012-02-14 13:02 Richard Ems
[not found] ` <4F3AA191.9030606@mnsu.edu>
2012-02-14 18:12 ` Richard Ems
2012-02-14 19:07 ` Christoph Hellwig
2012-02-15 12:48 ` Richard Ems
2012-02-14 23:10 ` Stan Hoeppner
2012-02-15 15:54 ` Richard Ems
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=4F3A2DE9.5050901@cape-horn-eng.com \
--to=richard.ems@cape-horn-eng.com \
--cc=hch@infradead.org \
--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