Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!munnari.oz.au!murdu!ucsvc.ucs.unimelb.edu.au!wehi!baxter_a
From: BAXTER_A@wehi.dn.mu.oz
Newsgroups: comp.sys.amiga.tech
Subject: Re: Memory Protection!!
Message-ID: <11940@wehi.dn.mu.oz>
Date: 29 Aug 90 10:59:43 GMT
References: <1145.26bd4989@waikato.ac.nz> <1410050@hpcvca.CV.HP.COM> <6423@sugar.hackercorp.com> <6424@sugar.hackercorp.com>
Organization: Walter & Eliza Hall Institute
Lines: 16

In article <6424@sugar.hackercorp.com>, peter@sugar.hackercorp.com (Peter da Silva) writes:
> One more comment on the overhead of malloc and free.
> 
> "Tracers" uses malloc and free internally, and still runs fast enough that
> it's unplayable at 21 volts on a standard A1000. Any time you're using malloc
> the free will be lost in the noise. If speed is that important you should
> probably be using a more efficient memory management mechanism than malloc
> anyway, like a set of fixed size buffer pools or something.
> -- 
> Peter da Silva.   `-_-'
> <peter@sugar.hackercorp.com>.

Multiplot (now with log axes) tracks memory resources and frees on the fly and
it still runs 10x faster than Cricket graph with a one bit plane screen.

Regards Alan