Marc-Andre Lemburg added the comment: We had a similar discussion a while back for pybench. Consensus then was to use the minimum as basis for benchmarking:
https://mail.python.org/pipermail/python-dev/2006-June/065525.html I had used the average before this discussion in pybench 1.0: https://mail.python.org/pipermail/python-announce-list/2001-November/001081.html There are arguments both pro and con using min or avg values. I'd suggest to display all values and base the findings on all available values, rather than just one: min, max, avg, median, stddev. ---------- nosy: +lemburg title: Enhance the timeit module -> Enhance the timeit module: display average +- std dev instead of minimum _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28240> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
