Lost time while profiling

[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.

-- 
Greg Ewing, Computer Science Dept,
University of Canterbury,	
Christchurch, New Zealand
http://www.cosc.canterbury.ac.nz/~greg