In article <20150403131050.GQ29270@platypus.pepperfish.net>,
Rob Kendrick <rjek@netsurf-browser.org> wrote:
> On Fri, Apr 03, 2015 at 01:30:14PM +0100, netsurf@avisoft.f9.co.uk wrote:
> > In article <54ae82a927chris@chris-johnson.org.uk>,
> > cj <chris@chris-johnson.org.uk> wrote:
> > > I can see why RISC OS gets indigestion with the cache. Have just
> > > deleted the cache on the Iyonix, and there were over 21,000
> > > directories and over 19,000 files.
> >
> > Yes, there seem to be lots of directories - many empty. The non-empty
> > ones often only contain directories. And the ones containing files
> > rarely have more than 1 file in!
> >
> > Strikes me that there are too many directory levels. Insetad of having
> > !Cache.Caches.Default.NetSurf.m.A.3.G.A3GKETD
> > it may be better to have
> > !Cache.Caches.Default.NetSurf.mA3G.A3GKETD
> >
> > I suspect much of the delay for small files is due to checking,
> > creating, and traversing directories!
> The depth was chosen so it would work on poor-quality file systems that
> only allow a handful of entries in a directory, such as FileCore :)
It is a shame that there is no simple way to discover if 'big
directories' are being used with no such limitations, as they have been
here for many many years.
Martin
No comments:
Post a Comment