A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2006-June/065541.html below:

[Python-Dev] Python Benchmarks

[Python-Dev] Python Benchmarks [Python-Dev] Python BenchmarksFredrik Lundh fredrik at pythonware.com
Fri Jun 2 15:49:46 CEST 2006
M.-A. Lemburg wrote:

> I believe that using wall-clock timers
> for benchmarking is not a good approach due to the high
> noise level. Process time timers typically have a lower
> resolution, but give a better picture of the actual
> run-time of your code and also don't exhibit as much noise
> as the wall-clock timer approach.

please stop repeating this nonsense.  there are no "process time timers" in con-
temporary operating systems; only tick counters.

there are patches for linux and commercial add-ons to most platforms that lets
you use hardware performance counters for process stuff, but there's no way to
emulate that by playing with different existing Unix or Win32 API:s; the thing
you think you're using simply isn't there.

</F> 



More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4