This is a kind of example where our GC card marking does not quite work. I think the improve-rdict branch should improve this kind of code quite a bit (but I still have to finish it)
On Tue, Apr 30, 2013 at 6:51 PM, Armin Rigo <ar...@tunes.org> wrote: > Hi, > > On Tue, Apr 30, 2013 at 5:26 AM, cat street <gam...@gmail.com> wrote: >> You can test this code: >> (...) > > For no good reason it seems that on this example CPython is quite a > bit faster on Linux64 than on Linux32. PyPy is also a bit faster on > Linux64 but not by such a large margin. In my tests (PyPy vs CPython) > it ends up the same on Linux32, and on Linux64 PyPy is a bit slower > (20%?). I think it's good enough given the type of code (completely > unoptimizable as far as I can tell, unless we go for "we can kill the > whole loop in this benchmark", which is usually a bit pointless in > real code). If others want to look in detail at JIT traces, feel free > to. > > > A bientôt, > > Armin. > _______________________________________________ > pypy-dev mailing list > pypy-dev@python.org > http://mail.python.org/mailman/listinfo/pypy-dev _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
