Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!uw-beaver!mit-eddie!bu-cs!dartvax!eleazar.dartmouth.edu!earleh
From: earleh@eleazar.dartmouth.edu (Earle R. Horton)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MPW garbage collection
Message-ID: <10237@dartvax.Dartmouth.EDU>
Date: 30 Sep 88 01:43:06 GMT
References: <208@tekn01.chalmers.se>
Sender: news@dartvax.Dartmouth.EDU
Reply-To: earleh@eleazar.dartmouth.edu (Earle R. Horton)
Organization: Society to make my life more fun.
Lines: 27

In article <208@tekn01.chalmers.se> d83_sven_a@tekn01.chalmers.se 
	(Sven (Sciz) Axelsson) writes:
>Question: What does MPW 2.0.x do when it put up its bulldoozer-cursor? I 
>suppose some sort of garbage collection takes place, but why is it so
>slooow? I used dumpcode to check out a code segment of about 40K on my
>SE. MPW went away bulldoozering twice; first time for five minutes, second
>time for nearly eight minutes. Cannot be a good implementation, can it?
>

You didn't say, but if you are running MPW Shell on a 1 Meg machine,
then you are at a disadvantage.  MPW really wants a full Megabyte to
itself, and the System Heap on 1 Meg machines takes a big chunk out of
this.  Also, if you are letting dumpcode put its output into a window,
more memory is needed than if you redirect the output to a file, then
open the file later.

"Dumpcode {parameters} > outputfile" is much faster than "dumpcode
{parameters}" no matter how much memory you have.

I must admit that I haven't seen the 'dozer at all since the people
who own this machine got me 5 Megs.  I hope the memory prices go down
before I have to give it back and use my own.


Earle R. Horton. 23 Fletcher Circle, Hanover, NH 03755
(603) 643-4109
Sorry, no fancy stuff, since this program limits my .signature to three