public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@soleranetworks.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Severe VFS Performance Issues 2.6 with > 95000 directory entries
Date: Sat, 12 Nov 2005 20:48:23 -0700	[thread overview]
Message-ID: <4376B787.9000108@soleranetworks.com> (raw)


The subject line speaks for itself.   This is using standard VFS readdir 
and lookup calls through the VFSwith ftp.  Very poor. 
It appears dcache related since longer file names proportionately take 
longer based on the size of the name.  My lookup routines use static 
pinned tables in memory, and are very fast.  VFS peformance non-ftp are 
reasonable, but still have problems with the number of entries
in a directory gets above 50,000.

Jeff

             reply	other threads:[~2005-11-13  5:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-13  3:48 Jeff V. Merkey [this message]
2005-11-13 12:45 ` Severe VFS Performance Issues 2.6 with > 95000 directory entries Nikita Danilov
2005-11-13 21:01   ` jmerkey
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=4376B787.9000108@soleranetworks.com \
    --to=jmerkey@soleranetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    /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