Lost time while profiling
François Pinard
pinard at iro.umontreal.ca
Tue Dec 3 21:40:31 EST 2002
[Greg Ewing]
> François Pinard wrote:
> > While running it under the Python 2.2.1 profiler, the profiler reports a
> > total number of CPU seconds which account for about 40% of the wall-clock
> > time. I wonder where the remaining time has gone!
> Probably it's the time used by the profiler itself. The profiler
> attempts to subtract its own overhead and report only the time used by
> your code.
According to the documentation for the `profile' module, this requires
prior calibration (the documentation explains how). When calibration
is not done, the documentation says that no correction is attempted.
In the sources, `profile.Profile.bias' is initialised to zero.
--
François Pinard http://www.iro.umontreal.ca/~pinard
More information about the Python-list
mailing list