Message-ID: <20000430214124.4616.qmail@nwcst318.netaddress.usa.net>
Date: 30 Apr 00 15:41:24 MDT
From: Joseph Morris <b52g AT usa DOT net>
To: opendos AT delorie DOT com
Subject: Re: Optimising disk access in DRDOS
X-Mailer: USANET web-mailer (M3.4.0.33)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id RAA29271
Reply-To: opendos AT delorie DOT com

> "YoYo" <YoYo AT wxc DOT net> wrote:
> Hi Joseph,
>
> As always, excuse me for my poor english.

> Smartdrv uses MUCH more mem itself (38 vs 22 kB),and is not much faster.

Not for me.  For building the program's scriptfiles smartdrv was orders of
magnitude faster than nwcache.

> You can improve the working of both programs with larger buffers.

I have already set the buffer and delay sizes for optimium performance
unfortunately.

> Caching always depend on how big the files are, how many it are and how
> often you access them.

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?

> Use diskopt or defrag frequently.

I'm not sure this will make much odds, since the program is being developed
and the separate files are therefore volatile and may change a lot.  But I'll
try it anyway. lot.  But I'll try it anyway.

____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1