Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!lsr
From: lsr@Apple.COM (Larry Rosenstein)
Newsgroups: comp.sys.mac.programmer
Subject: Re: profiling and speeding up Mac code
Message-ID: <12123@goofy.Apple.COM>
Date: 15 Feb 91 21:26:10 GMT
References: <2196.27B7FD50@stjhmc.fidonet.org> <23166@well.sf.ca.us>
Organization: Apple Computer, Inc.
Lines: 22

In article <23166@well.sf.ca.us> oster@well.sf.ca.us (David Phillip Oster) writes:
>
>I don't understand. If you crank the beachball every time you've done 100th
>of the work, and it takes a 1000th of the total CPU time each time you
>crank it, how does speeding up the CPU change these ratios?

It depends on what you want to convey.  If you want to show how fast the
program is running then you're correct.  On a faster machines the
appropriate checkpoints occur faster and the beachball turns faster.

If the goal is just demonstrate progress, and run in the background (but not
show how fast progress is being made), then it is better to rotate the
cursor based on ticks.  Each time the cursor changes, MPW yields the CPU to
background tasks.  The more often the cursor changes the less CPU time the
tool gets.


-- 
		 Larry Rosenstein,  Object Specialist
 Apple Computer, Inc.  20525 Mariani Ave, MS 3-PK  Cupertino, CA 95014
	    AppleLink:Rosenstein1    domain:lsr@Apple.COM
		UUCP:{sun,voder,nsc,decwrl}!apple!lsr