Date: Mon, 1 May 2000 13:36:17 +0200 (MET DST)
Message-Id: <3.0.16.19900501133423.302fccb0@tellus.swip.net>
X-Sender: mt58779 AT tellus DOT swip DOT net
X-Mailer: Windows Eudora Pro Version 3.0 Demo (16)
To: opendos AT delorie DOT com
From: Bernie <bernie AT mbox302 DOT swipnet DOT se>
Subject: Re: Optimising disk access in DRDOS
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Reply-To: opendos AT delorie DOT com

Joseph Morris wrote:
>The problematic task is loading approx 6MB of data into memory from a number
>of files in a directory tree.  For development purposes each file can come
>from one of three locations and each must be checked in turn before deciding
>which version of the file to load, since files from some locations can
>override others.
>
>So there is not only the loading but also checking for existence of files
>(which the profiler claimed was a bottleneck).
>
>With this in mind, what would be the optimum caching arrangement?

A disk cache that can handle more than 7 MB would probably help (SmartDrv
from Win95 OSR2 has a max at ca 36.5M). Another thing you can do is to put
your temp directory on a ramdrive, with 96MB of RAM allocating 32MB for a
ramdrive (and 36.5 for disk cache) you'll still have plenty of memmory left.
Putting command.com on the ramdrive (and changing the comspec setting) will
also speed up things (if you often exit programs that have made command.com
being unloaded or the program uses comspec).
To increase the speed for finding files you should remove all files that
you don't need.
//Bernie
http://bernie.arachne.cz/ DOS programs, Star Wars ...