Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!apple!vsi1!ubvax!ardent!peck!rap
From: rap@peck.ardent.com (Rob Peck)
Newsgroups: comp.sys.amiga.tech
Subject: Re: dos_stuff
Keywords: Spam,dos,spamalopes
Message-ID: <8682@ardent.UUCP>
Date: 12 Oct 89 16:35:49 GMT
References: <5571@ucdavis.ucdavis.edu>
Sender: news@ardent.UUCP
Reply-To: rap@peck.ardent.com (Rob Peck)
Organization: Ardent Computer Corp., Sunnyvale, CA
Lines: 18

In article <5571@ucdavis.ucdavis.edu> rogers@iris.ucdavis.edu (Brewski Rogers) writes:
>
>So putting all my little files into one big file should help too?
>the big file would be about 500K in that case, and a typical load
>of a map would need to go through just about the whole thing reading
>in the 120K of data it wanted.


Somehow I believe that if you are using this superfile thing and using
seek commands from AmigaDOS or fseek() from a compiler would retrieve the
file quite a bit more quickly than "go through just about the whole thing".
Presumably you maintain an index of  what data it needs at a particular
point, and can therefore build a table of indexes off of which to seek
to get there.  I never found out quite HOW AmigaDOS finds a particular
sector, but I doubt that it would have to read an entire file each time
just to do a seek to a particular position.

Rob Peck