And if you are using Panther you can achieve the same thing by
calling on an
AppleScript Studio app instead of Automator.
Yes, that's cool. However you get a coarser granularity than with
chrono.
OM(BN)M, Automator says 0.002, while chrono says 0.0002.
Which hardly matters if the margin of error is significantly larger
than either measurement. If the limit of precision is only ±0.1 sec
then it doesn't matter if your timer gives 0.002 or 0.0002 sec as
its result because they're both rubbish data. Accuracy, not
resolution, is the limiting factor that requires timing brief
operations over multiple iterations.
I am sorry, but your analysis is wrong. The significancy of your
measurement is determined by the instrument you use to measure.
Assuming your precision is ±0.1 before knowing the instrument to
measure is a flaw.
(Hint: Anyone who wants to profile and optimise their code really
needs to do their homework on the subject first, else they'll just
end up wasting their time.)
