timeit.repeat() inaccuracy on W2K?

[Dennis Benzinger]

I just played around with the new timeit module.
Using the following code I get some strange results:

import timeit

def test(s):
result = 0
for c in s:
result += ord(c)
return result

t = timeit.Timer("t est('dennisbenz inger')", "from __main__ import test")
print t.repeat(number =50000)

Most of the time I get a result like

[3.3263199652469 799, 3.3338471789012 294, 3.3557058229467 716] with all execution times are about 3.

But sometimes I get something like [3.3410785448988 629, 4802.7882074397 721, 1203.1983464378 854]

where one or two execution times are much higher than the other
ones, although the program took about the same time to execute
and certainly not some thousand times as long...

I'm running Python 2.3.2 on Windows 2000 with ServicePack 4

[Raymond Hettinger]

"Dennis Benzinger" <De************ **@gmx.net> wrote in message
news:3f******** @news.uni-ulm.de...

I just played around with the new timeit module.
Using the following code I get some strange results:

import timeit

def test(s):
result = 0
for c in s:
result += ord(c)
return result

t = timeit.Timer("t est('dennisbenz inger')", "from __main__ import test")
Perhaps there is something awry with the default windows timer, so try this
instead:

t = timeit.Timer("t est('dennisbenz inger')", timer=time.time , "from __main__
import test")
But sometimes I get something like

>> [3.3410785448988 629, 4802.7882074397 721, 1203.1983464378 854]

where one or two execution times are much higher than the other
ones, although the program took about the same time to execute
and certainly not some thousand times as long...

I once saw an issue like this and the underlying cause turned out to be having
two tick counters on a multi-processor machine.
Raymond Hettinger