From: Dave Chinner <david@fromorbit.com>
To: hank peng <pengxihan@gmail.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: how to increase speed to iterate all file's name in a XFS , about million files.
Date: Wed, 29 Sep 2010 10:48:09 +1000 [thread overview]
Message-ID: <20100929004809.GI5665@dastard> (raw)
In-Reply-To: <AANLkTikd2Gf-=jimO-OvKb-66UquPkjfCN=+bx-3fhY-@mail.gmail.com>
On Wed, Sep 29, 2010 at 08:28:08AM +0800, hank peng wrote:
> Hi:
> I have a XFS file system which contains about million files in it. I
> want to iterate all file's name using readdir function and I found
> that a little time-consuming.
> Anybody to suggest a way to increase its speed?
In what way was it time consuming? IO bound? CPU bound? something
else?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-29 0:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 0:28 how to increase speed to iterate all file's name in a XFS , about million files hank peng
2010-09-29 0:48 ` Dave Chinner [this message]
2010-09-29 0:55 ` hank peng
2010-09-29 1:01 ` 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=20100929004809.GI5665@dastard \
--to=david@fromorbit.com \
--cc=linux-xfs@oss.sgi.com \
--cc=pengxihan@gmail.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