On Sat, Aug 20, 2011 at 09:48 +0200, Maciej Fijalkowski wrote: > On Sat, Aug 20, 2011 at 8:15 AM, holger krekel <hol...@merlinux.eu> wrote: > > On Fri, Aug 19, 2011 at 23:52 +0200, Maciej Fijalkowski wrote: > >> On Fri, Aug 19, 2011 at 7:35 PM, holger krekel <hol...@merlinux.eu> wrote: > >> > Congrats also from here! > >> > > >> > On the plus side pytest's own test suite passes all tests, even some > >> > which > >> > are marked as "expected-to-fail" with cpython-2.7. On the minus side, > >> > the whole test run is still 2-3 times slower compared to cpython which > >> > is slightly worse than with pypy-1.5. of course there is not too much to > >> > JIT but > >> > still a bit of a dissappointing result. > >> > >> Well, yes, but also we have no good answer to this. I think the reason > >> why it got slower is because we compile functions now as well (which > >> takes extra time). Test suites are hard I fear :( > > > > Maybe worth a small note because i guess test suites are often run to test > > pypy. > > A small note where?
at places where people read it ... nevermind :) > > FWIW if i run the test suite with --jit off it takes 117 seconds instead of > > 72 with JIT (cpython takes about 25 seconds). So maybe one question is > > why pypy-no-jit is already 4-5 times slower to begin with. > > I guess a lot of things come into play - pypy's interpreter is > generally slower than CPython's interpreter. We can attribute this to > many things, but we were so far happy with "we pay 2x for abstraction > layer". Maybe it's not good enough any more and we can actually come > up with a better interpreter, who knows. sure, i know about the 2x bit - it's not that i never developed core pypy or wrote various reports and bits about all these issues :) I am talking of 4-5 times slower, though, and that seems a bit much, doesn't it? holger _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
