Nathaniel Smith, 24.08.2010 18:48: > On Sun, Aug 22, 2010 at 11:57 PM, Kay Hayen wrote: >> I currently only have "pystone" as a benchmark, which is a bit >> difficult to look at, because it's not good at telling you why it has >> that speed, aggregating everything into one. > > You might want to take advantage of the work the Unladen Swallow folks > have put into benchmark tooling: > http://code.google.com/p/unladen-swallow/wiki/Benchmarks
Yes, pystone and pybench are particularly bad benchmarks for translation to C code. Pybench even has a benchmark that simply assigns numbers to variables. When compiled into optimised C code, this becomes useless code that the C compiler discards. So the benchmark sometimes fails because it can happen that it runs a tiny bit faster than even the calibration loop. Stefan _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
