Maciej Fijalkowski: > http://buildbot.pypy.org/nightly/trunk/
Thanks. > For what is worth, you picked up a very terrible program - this > program exercises long implementation, not "how fast you run python > programs". A new pypy is ~30% slower than cpython, which we find > reasonable (because it's runtime time), if you want faster pick gmpy. > GMP however has no means of recovering from a MemoryError. It was an example from a given context. Clearly, it doesn't show many different features to optimize. > How do you want to benchmark python compilers on this? Can anyone do > something more sensible than just call operations on longs? I compared it also with a version with serialized tuple assignments which shows an improvement of around 2.5 % on CPython, but no real change on PyPy, which is kind of what I hoped. Regards, Dinu _______________________________________________ pypy-dev mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-dev
