[Python-checkins] r46146 - sandbox/trunk/rjsh-pybench/pybench.py

[M.-A. Lemburg]

Tim Peters wrote:
> [M.-A. Lemburg]
>> Hmm, then I don't understand why I get weird results from the
>> GetProcessTimes() API.
>>
>> I'll have to do some more testing.

While converting the IDLE interactive session into a usable
test script, I found that the IDLE interface must have been
playing some tricks on me: running the module on its own
created more reasonable results.

I've attached the script below. I'm not sure whether the 100ns
interval mentioned in the win32 docs is correct. The times
I'm getting is 2.25 seconds for the load part on Linux and
0.295 seconds on Windows. It's possible that the values returned
for UserTime and KernelTime are in fact micro-seconds.

>> It's possible that the Windows API has a different understanding
>> of what "user time" refers to than e.g. Linux does.
> 
> It might be helpful to post the code you're using, and describe what
> you did with it in sufficient detail so that others could confirm or
> deny they see the same thing on their Windows box.

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, May 25 2006)
>>> Python/Zope Consulting and Support ...        http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ...             http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
________________________________________________________________________

::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: time_clock.py
Url: http://mail.python.org/pipermail/python-checkins/attachments/20060525/e60c1a26/attachment.asc