Path: utzoo!mnetor!uunet!husc6!think!ames!elroy!mahendo!jplgodo!wlbr!scgvaxd!stb!remsit!michael
From: michael@remsit.UUCP (Michael Gersten)
Newsgroups: comp.sys.amiga
Subject: Re: Fastbench
Message-ID: <442@remsit.UUCP>
Date: 5 Dec 87 02:38:38 GMT
References: <6888@sunybcs.UUCP> <7795@g.ms.uky.edu>
Reply-To: michael@remsit.UUCP (Michael Gersten)
Organization: REM's IT, Santa Monica, CA
Lines: 29

In article <7795@g.ms.uky.edu> sean@ms.uky.edu (Sean Casey) writes:
>In article <6888@sunybcs.UUCP> ugpete@sunybcs.UUCP (Peter Theobald) writes:
>>   AmigaDog is VERY fast at looking up files it already knows the names
>>of (it can go right to them because of the hash tables) so opening a
>>workbench drawer is now a process of getting '.info.dir' then getting each
>>.info file in the list. Very fast!
>>   Workbench would have to be changed as follows: Each time a .info file is
>>deleted or a new .info file is created, the .info.dir in that directory
>>must be updated. Note that if a .info file is merely altered the .info.dir
>>is still valid and doesn't have to be changed.

Workbench already does this. The problem is that it usually winds up going
to a new track. The system only cache's sectors that were requested, so
10 sectors (5K of data folks) gets thrown out.

>Better yet, do the right thing and fix Amigados and associated programs so
>that directory accesses go as quickly as they could.

All you need to do is tell the trackdisk.device to cache TRACKS, not just
the 5 most recent sectors. 

Speaking of which, C=, can we please get the 1.1 file system BACK in 1.3?
You think I'm crazy? Imagine what happens when a track dies. Under 1.1
you lost one file or 11 file names. Under 1.2 you lose one file or
5 file names and 5 files. 

(Guess what happened to me recently?)

				Michael