Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!stjhmc!p88.f15.n300.z1.fidonet.org!Lawson.English
From: Lawson.English@p88.f15.n300.z1.fidonet.org (Lawson English)
Newsgroups: comp.sys.mac.programmer
Subject: Re: profiling and speeding up Mac code
Message-ID: <2957.27C0AAA4@stjhmc.fidonet.org>
Date: 16 Feb 91 21:16:02 GMT
Sender: ufgate@stjhmc.fidonet.org (newsout1.26)
Organization: FidoNet node 1:300/15.88 - Tucson Apple Core, Tucson AZ
Lines: 26

David Phillip Oster writes in a message to All

DPO> I don't understand. If you crank the beachball every time you've 
DPO> done 100th of the work, and it takes a 1000th of the total CPU 
DPO> time each time you crank it, how does speeding up the CPU change 
DPO> these ratios

It depends on the hardware/software that is drawing the beachball. It doesn't
necessarily follow that 1/1000 of the CPU time on one Mac to draw the ball is
the same as 1/1000 of the time on another, or on the same Mac with an accellerator.
If you are actually doing 1 turn every 1000 widgets, there probably won't be
a problem, but some programs seem to spin the little ball so fast that it looks
like a blur. The little ball might be eating 50% (or more) of your time at that
speed.

Tom Dowdy pointed out to me that the "when" field of the EventRecord can be
used to time the turns of the cursor. If you don't want to call GetNextEvent
then TickCount might be used.


Lawson
 

--  
Uucp: ...{gatech,ames,rutgers}!ncar!asuvax!stjhmc!300!15.88!Lawson.English
Internet: Lawson.English@p88.f15.n300.z1.fidonet.org