On 04/12/2011 06:02 AM, Stefan Behnel wrote: > Maciej Fijalkowski, 11.04.2011 11:53: >> I propose the waf benchmark removal. >> >> Originally, the idea was that we're slower than CPython for no good >> reason. Now that this benchmark measures some obscure piece of stdlib >> time (subprocesses) I don't think it's that necessary. >> >> Besides: >> >> * the variation between runs is too big, so we don't care >> * noone was ever remotely interested in speeding this up >> >> any opinions? > > Despite the relatively large variations, Cython runs this benchmark > persistently ~1/3 faster than CPython 2.7 for me - minus the currently > missing support for "__file__", which is used at build time here. So my > vote would be to leave it in, maybe someone has an incentive to speed this > up once you have bars up for Cython. :)
I could look at the waf script used for the benchmark so that it depends more on python performances. One thing which is annoying in all the python build tools (waf, scons, etc...) is that when you use multiple builds with python-based build functions, it is slower than with a single job. That's a bottleneck for the waf-based build of numpy, at least. cheers, David _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
