Possible inaccuracy in Python 2.4 when using profiler calibration

Dieter Maurer dieter at handshake.de
Fri Jun 16 20:40:18 CEST 2006


Brian Quinlan <brian at sweetapp.com> writes on Thu, 15 Jun 2006 10:36:26 +0200:
> I have a misinformed theory that I'd like to share with the list.
> 
> I believe that profiler calibration no longer makes sense in Python
> 2.4 because C functions are tracked and they have a different call
> overhead than Python functions (and calibration is done only using
> Python functions). Here is my reasoning (in code form):

I fear it never made sense -- even with pure Python functions:

  I tried to calibrate under Linux and failed miserably:
  apparently, the "clock" resolution is very coarse
  introducing a very high variance which is very bad for
  calibration.



More information about the Python-list mailing list