From: ebiederm@xmission.com (Eric W. Biederman)
To: Andreas Dilger <adilger@shaw.ca>
Cc: jmerkey <jmerkey@utah-nac.org>, Andrew Morton <akpm@osdl.org>,
strombrg@dcs.nac.uci.edu, linux-kernel@vger.kernel.org
Subject: Re: huge filesystems
Date: 19 Mar 2005 04:06:17 -0700 [thread overview]
Message-ID: <m1fyyr28uu.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20050315060444.GC31960@schnapps.adilger.int>
Andreas Dilger <adilger@shaw.ca> writes:
> On Mar 14, 2005 21:37 -0700, jmerkey wrote:
> > 1. Scaling issues with readdir() with huge numbers of files (not even
> > huge really. 87000 files in a dir takes a while
> > for readdir() to return results). I average 2-3 million files per
> > directory on 2.6.9. It can take a up to a minute for
> > readdir() to return from initial reading from on of these directories
> > with readdir() through the VFS.
>
> Actually, unless I'm mistaken the problem is that "ls" (even when you
> ask it not to sort entries) is doing readdir on the whole directory
> before returning any results. We see this with Lustre and very large
> directories. Run strace on "ls" and it is doing masses of readdirs, but
> no output to stdout. Lustre readdir works OK on directories up to 10M
> files, but ls sucks.
The classic test is does 'echo *' which does the readdir but not the
stat come back quickly?
Anyway most of the readdir work is in the filesystem so I don't see
how the VFS would be involved....
Eric
next prev parent reply other threads:[~2005-03-19 11:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 18:53 huge filesystems Dan Stromberg
2005-03-09 19:37 ` Chris Wedgwood
2005-03-09 22:01 ` Miklos Szeredi
2005-03-14 16:41 ` Andreas Dilger
2005-03-14 16:56 ` jmerkey
2005-03-15 3:21 ` Andrew Morton
2005-03-15 3:37 ` jmerkey
2005-03-15 4:02 ` Andrew Morton
2005-03-15 4:37 ` jmerkey
2005-03-15 6:04 ` Andreas Dilger
2005-03-19 11:06 ` Eric W. Biederman [this message]
2005-03-15 9:28 ` Barry K. Nathan
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=m1fyyr28uu.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=adilger@shaw.ca \
--cc=akpm@osdl.org \
--cc=jmerkey@utah-nac.org \
--cc=linux-kernel@vger.kernel.org \
--cc=strombrg@dcs.nac.uci.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.