From: jmerkey <jmerkey@soleranetworks.com>
To: Nikita Danilov <nikita@clusterfs.com>
Cc: Linux Kernel Mailing List <Linux-Kernel@vger.kernel.org>
Subject: Re: Severe VFS Performance Issues 2.6 with > 95000 directory entries
Date: Sun, 13 Nov 2005 14:01:13 -0700 [thread overview]
Message-ID: <4377A999.7090305@soleranetworks.com> (raw)
In-Reply-To: <17271.13688.298525.23645@gargle.gargle.HOWL>
Nikita Danilov wrote:
>Jeff V. Merkey writes:
> >
> > The subject line speaks for itself. This is using standard VFS readdir
> > and lookup calls through the VFSwith ftp. Very poor.
>
>Reiser4 works fine with 100M entries in a directory, so VFS is not a
>bottleneck here.
>
>
how about with ftp running on top? Try running FTP in directory with
100M entries. See how long it takes to return the data to
the remote client for a dir listing.
Jeff
>[...]
>
> >
> > Jeff
>
>Nikita.
>
>
>
next prev parent reply other threads:[~2005-11-13 21:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-13 3:48 Severe VFS Performance Issues 2.6 with > 95000 directory entries Jeff V. Merkey
2005-11-13 12:45 ` Nikita Danilov
2005-11-13 21:01 ` jmerkey [this message]
2005-11-13 21:34 ` Nikita Danilov
2005-11-13 21:24 ` jmerkey
2005-11-13 21:50 ` Douglas McNaught
2005-11-13 21:28 ` jmerkey
2005-11-13 21:37 ` Jeff V. Merkey
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=4377A999.7090305@soleranetworks.com \
--to=jmerkey@soleranetworks.com \
--cc=Linux-Kernel@vger.kernel.org \
--cc=nikita@clusterfs.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