[Python-Dev] Python Benchmarks (original) (raw)
M.-A. Lemburg mal at egenix.com
Tue Jun 6 16:59:43 CEST 2006
- Previous message: [Python-Dev] Python Benchmarks
- Next message: [Python-Dev] Python Benchmarks
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Fredrik Lundh wrote:
M.-A. Lemburg wrote:
I just had an idea: if we could get each test to run inside a single time slice assigned by the OS scheduler, then we could benefit from the better resolution of the hardware timers while still keeping the noise to a minimum.
I suppose this could be achieved by: * making sure that each tests needs less than 10ms to run iirc, very recent linux kernels have a 1 millisecond tick. so does alphas, and probably some other platforms.
Indeed, that's also what the microbench.py example that I posted demonstrates.
And of, course, you have to call time.sleep() before running the test (which microbench.py does).
-- Marc-Andre Lemburg eGenix.com
Professional Python Services directly from the Source (#1, Jun 06 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 ! ::::
- Previous message: [Python-Dev] Python Benchmarks
- Next message: [Python-Dev] Python Benchmarks
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]