[Python-Dev] Stop using timeit, use perf.timeit! (original) (raw)
Meador Inge meadori at gmail.com
Fri Jun 10 14:47:19 EDT 2016
- Previous message (by thread): [Python-Dev] Stop using timeit, use perf.timeit!
- Next message (by thread): [Python-Dev] Stop using timeit, use perf.timeit!
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Jun 10, 2016 at 6:13 AM, Victor Stinner <victor.stinner at gmail.com> wrote:
The second result is a new perf module which includes all "tricks"
discovered in my research: compute average and standard deviation, spawn multiple worker child processes, automatically calibrate the number of outter-loop iterations, automatically pin worker processes to isolated CPUs, and more.
Apologies in advance if this is answered in one of the links you posted, but out of curiosity was geometric mean considered?
In the compiler world this is a very common way of aggregating performance results.
-- Meador -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20160610/b96da5aa/attachment.html>
- Previous message (by thread): [Python-Dev] Stop using timeit, use perf.timeit!
- Next message (by thread): [Python-Dev] Stop using timeit, use perf.timeit!
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]