Guido van Rossum wrote:
My nightly run of pybench went up from the usual 7590ms per run to around 8200ms between Monday night and today. Can anyone explain this ?
Did you compare the outputs? There could be importants hint there! :-)
Unfortunately, the cronjob always uses the same file to store the benchmark data (I've changed that now, to be able to check on a day-per-day basis).
Is there a way to check out a Python CVS version dated 2003-02-24 ? I could then give that a try again.
Maybe this checkin to ceval.c backfired?
revision 2.351 date: 2003/02/26 18:11:50; author: rhettinger; state: Exp; lines: +18 -4 Micro-optimizations.
- List/Tuple checkexact is faster for the common case.
- Testing for Py_True and Py_False can be inlined for faster looping.
Could be. I don't think inlining in ceval will help. The switch is too long already and it's much better to let the compiler/processor decide which parts should really get inlined since they have more knowledge about the platform than we do (sometimes :-).