STINNER Victor added the comment: I believe that this issue was indirectly fixed by the issue #26275. The new flavor of the benchmark suite now calibrates (computes the number of outter loop iterations) each benchmark based on time, no more using a fixed number of loop iteartions.
Brett: Can you please confirm that the issue was fixed in the new performance benchmark suite? https://github.com/python/performance -------- $ python3 -m performance run -b silent_logging,unpack_sequence --fast -o json Python benchmark suite 0.1.3dev (...) Report on Linux smithers 4.5.7-300.fc24.x86_64 #1 SMP Wed Jun 8 18:12:45 UTC 2016 x86_64 x86_64 Total CPU cores: 8 ### logging/no_output ### Median +- std dev: 809 ns +- 16 ns ### unpack_sequence ### Median +- std dev: 120 ns +- 4 ns -------- * silent_logging used 10 inner-loops and 2^14 outter-loops * unpack_sequence used 400 inner-loops and 4096 outter-loops You can you this using the "python3 -m perf dump -v json" command on the output JSON file (search for "loop"). ---------- nosy: +haypo _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25423> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
