[ Quoting Denis Tonn to Jamie Walker ] 
 JW> The resizing algorithm is quite simple. If something is 
 DT> This is one of the most inefficient ways to handle dynamic cache 
 DT> sizing. It is not predictive in any way, and leads to lots of system
Windows will leave around 1 meg free, when possible. In 32meg RAM, if my
computer is idle (a few tasks open, not doing anything), the cache grows to
13.5 meg, with around 950k free. Win will try to keep this memory free so 
hat
it is instantly available. When something starts using LOTs of memory (eg
netscape), Win will start dumping chunks of cache. In my case, 2 meg at a
time, twice.
I think windows also reports free memory to programs as free memory + cache
size (+ swap file). I've never seen the cache go below .5 meg either, even
in 8 meg machines.
 DT> not a function of dynamic caching, but a surfeit of RAM. The same
 DT> result could be achieved with a large static cache. 
True. I use a mixture of the two. I set my cache to stay below 8 meg, and
above 2 meg. It can do whatever it wants in between those values.
Regards,
 - Scott
[ admin@cyberia.asstdc.com.au | www.asstdc.com.au/~cyberia ]
--- FMail/Win32 1.22
3:712/848)
---------------