caching dirs

[prozak]

From a post on the forum by darkone himself I understand that the caching of dirs by io is handled by windows explorer itself. I.e. entering a direrctory either through explorer or ftp will cache whatever is listed (correct me if I am wrong) My problem is that I need the sorted directory to be cached because listing takes forever if it is not (roughly ten thousand dirs in the sorted dir). I hoped doing a manual search in explorer in that directory would be enough to cache the dirs but that didnt work. Does any one know a 'smart' way off caching that directory without acutally listing it through an ftp client? I know I can use the a fucnction like calculating ftp space used under that dir but im loking for a solution that would not require any manual interference. I would also like to know how to change the time before a user is disconnected when listing is slow. Entering a non cached large dir now will cause a 'connection lost' response by the server. Is there any way to change the time before that happens?

THanks in advance

[neoxed]

Originally posted by prozak
From a post on the forum by darkone himself I understand that the caching of dirs by io is handled by windows explorer itself. I.e. entering a direrctory either through explorer or ftp will cache whatever is listed (correct me if I am wrong)

You misunderstood him. ioFTPD's internal directory cache has absolutely nothing to do with Windows Explorer. ioFTPD only caches a directory once you "enter" it through an FTP client.

Originally posted by prozak
My problem is that I need the sorted directory to be cached because listing takes forever if it is not (roughly ten thousand dirs in the sorted dir).

There's no practical reason why one would have so many files and directories in a relatively shallow directory tree. Either clean-up/reorganize the directory structure or live with it.

[prozak]

THanks for your reply Neo. So from what I understand there is no way to have dirs automatically cached. As far as your comment stating that there is no reason to have that many dirs I obviously disagree . If one is to have a large site made easily accessable a mp3 sorted directory imo would qualify as an excellent reason to have that many directories. Can you think of any 'creative' way of forcing io to chache the dirs under that path?

THanks in advance.

*edit*

just to be clear, the sorted dir I refer to is organized by artist/genre etc in case you are thinking it is one directory with 10thousand dirs in it.

[Zer0Racer]

Make sure you set the dir caching options in ioFTPD.ini to something that can hold the number of files and dirs you have on your site. Only downside is io will use more memory, but still not alot. I currently use this:

DirectoryCache_Size		= 6000		# Amount of directories to cache per cache bucket (8 buckets)

Meaning my ioFTPD caches 48000 dirs, and it never uses more than 30MB memory.

Entering a dir containing huge amounts of files and subdirs will only be slow first time after ioFTPD is started. The cache is then built up and listing will be super fast. Don't think it matters if you get connection lost when you try the first time, cache is still built.

So the trick for you would be to log in and enter the dir yourself if you've restarted ioFTPD.