RE: [Visualpython-users] rate() function

[Bruce S. <bas...@un...>]

The crux of the matter seems to be the question, what is the accuracy of 
the Windows clock? On the Windows machine where I tried Gary's test routine 
and saw the bizarre results he reported, I got 700 loop/sec with no rate 
statement, which implies that one loop took 1.4 millisecond. If the clock 
is accurate to microseconds, no problem. If the clock is accurate to 15 ms 
(1/60 s?), it's hopeless.

Bruce Sherwood

At 03:45 PM 6/21/02 -0400, you wrote:
>The time slices used by Windows are often on the
>order of 15ms, which is quite a large margin of error in the type of
>test you are doing.


At 04:48 PM 6/21/02 -0400, Gary Strangman wrote:
>Interestingly, replacing the rate() call in my previous program with a
>spin-loop of the short you mentioned above (but based on time.clock(),
>which on Windows is supposed to be accurate down to microseconds), I still
>get the stair-stepping ...