Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!purdue!bu-cs!dartvax!eleazar.dartmouth.edu!erics
From: erics@eleazar.dartmouth.edu (Eric Schlegel)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MPW garbage collection
Message-ID: <10257@dartvax.Dartmouth.EDU>
Date: 3 Oct 88 01:40:25 GMT
References: <208@tekn01.chalmers.se>
Sender: news@dartvax.Dartmouth.EDU
Reply-To: erics@eleazar.dartmouth.edu (Eric Schlegel)
Organization: Dartmouth College, Hanover, NH
Lines: 16

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?

What is this bulldozer cursor? I've never seen it, and I've been using MPW 2.0
since the beta came out. I've also used dumpcode to dump some fairly large
resources, although perhaps not as large as 40K.

Eric
------
Eric Schlegel                 |  DISCLAIMER: I'm just a poor college student,
eric.schlegel@dartmouth.edu   |  which means I'm not responsible for what I
                              |  say and I can't pay you if you sue me anyway.