[Python-Dev] Stop using timeit, use perf.timeit! (original) (raw)
Victor Stinner victor.stinner at gmail.com
Fri Jun 10 17:22:42 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 ]
2016-06-10 20:47 GMT+02:00 Meador Inge <meadori at gmail.com>:
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.
FYI I chose to store all timings in the JSON file. So later, you are free to recompute the average differently, compute other statistics, etc.
I saw that the CPython benchmark suite has an option to compute the geometric mean. I don't understand well the difference with the arithmeric mean.
Is the geometric mean recommended to aggregate results of different (unrelated) benchmarks, or also even for multuple runs of a single benchmark?
Victor
- 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 ]