Re: Severe VFS Performance Issues 2.6 with > 95000 directory entries

[jmerkey]

Nikita Danilov wrote:

> jmerkey writes:
> > 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.
>
> Why are you thinking that it is VFS that is causing performance
> degradation here?
>  

Because I see the same degredation local vs. remote. My path for readdir 
and lookup are short. I dynamically (via math) create
the file names on the fly and lookup simply reads a static table in 
memory for inode number. One thing I can check are calls
to igetblk inside of lookup.

Jeff

> > 
> > Jeff
> > 
> > >[...]
> > >
> > > > 
> > > > Jeff
> > >
>
> Nikita.
>
> > >
> > >  
> > >
>
>  

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/