Hello Martin,

On 28-Apr-99, Martin Steigerwald wrote:
>> I dont know if this is an MD2 specific problem or if it relates moroe
>> generally to MUI, but basically...
>> 
>> Before starting MD2, I have around 43 libs resident on my system.
>> After MD2 is loaded, I have about 120 libs in memory.
>> After quitting MD2, the libs do not get flushed and remain there. Whilst
>> I agree that this speeds up MUI operations (and with 34Mb there isn't
>> much to worry about) it would be nice, however, if MD returned the
>> system to its initial state after use and exited more cleanly.
> 
> The default system behaviour is to keep libraries in memory unless a
> program asks for more memory that is actually free. In this case the
> system flushes libs, datatypes etc. 
> 
> I don't see why Ollie should change anything about this. Quite some
> speed of the Amiga is coming from this concept. A library is loaded
> once and does not need to be loaded again when a new program that uses
> it is loaded. And on Amiga those libraries are so small, why care?
> 
> The only thing that might get higher is memory fragmentation, but with
> 32MB or more this normally really isn't an issue. I have 48 MB here
> and even after 5 hours of work I have a free chunk of at least 20 MB.
> 

Well I have 140megs of fast here, and obvioussly no problem, but my wife has
only 8, most of it 16bit ram, and she has no trouble with Micordot.  The
memory flushing must work, or she would be in trouble.  I have seen her
biggest block get down to two megs, though, but that wass after running YAM,
not Microdot.

Regards,
-- 
Mike Leavitt  [EMAIL PROTECTED]  + team Amiga +



Reply via email to