[issue25423] Deprecate benchmarks that execute too quickly

Brett Cannon added the comment: I trust you fixed it. :) -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Py

[issue25423] Deprecate benchmarks that execute too quickly

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

[issue25423] Deprecate benchmarks that execute too quickly

Changes by Ezio Melotti : -- keywords: +easy nosy: +ezio.melotti stage: -> needs patch type: -> behavior ___ Python tracker ___ ___

[issue25423] Deprecate benchmarks that execute too quickly

Antoine Pitrou added the comment: I haven't seen that: $ ./perf.py -f -b silent_logging `which python2.7` `which python3.4` INFO:root:Automatically selected timer: time Running silent_logging... INFO:root:Running `/home/antoine/.local/bin/python3.4 ./performance/bm_logging.py -n 5 --timer time

[issue25423] Deprecate benchmarks that execute too quickly

New submission from Brett Cannon: I have seen both silent_logging and unpack_sequence reliably complete so quickly in fast mode as to be measured at 0 time. That indicates to me that the benchmarks are no longer measuring something of consequence. -- components: Benchmarks messages: 25