Path: utzoo!utgpu!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: profiling and speeding up Mac code
Message-ID: <2196.27B7FD50@stjhmc.fidonet.org>
Date: 11 Feb 91 15:32:27 GMT
Sender: ufgate@stjhmc.fidonet.org (newsout1.26)
Organization: FidoNet node 1:300/15.88 - Tucson Apple Core, Tucson AZ
Lines: 29

Kevin Michael Goldsmith writes in a message to All

KMG> I already know a bit about speeding up C code. Also, is there 
KMG> any sort of profiler that I can use to see where the mac is spending 
KMG> time in my code?

M'boss and I wrote a profiler some time ago (it broke with system 5.x if that
gives you aan idea of how long ago). The largest single bottleneck for the average
Mac Program is the trap dispatcher. Most people don't like to use it, but if
you have graphics-intensive code that uses lots of "pixel-plots" then you might
consider using it. Another fine bottleneck is overuse of the "spinning beachball"
ICON. If you let that thing turn every so many widgets, the faster the CPU,
the proportionately greater the overhead to use it. If you are doing math-intensive
stuff and aren't calling the FPP directly, you might consider jumping directly
to the Package, or, better (if you don't need SANE's accuracy), patch the SANE
Package to call the FFP for ALL math functions, instead of just the arithmatic
ones (of course, then you have to handle the SANE/IEEE conversions yourself,
but...). 


Hope this helps...


Lawson
 

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