On Mon, Jul 18, 2011 at 2:34 PM, Antonio Cuni <anto.c...@gmail.com> wrote: > On 18/07/11 14:10, Carl Friedrich Bolz wrote: >> offtopic, but I still want to point out that translate is indeed terribly >> messy. I've been reading traces some more, and it's quite >> scary. E.g. we have lltype._struct.__init__ has a CALL_FUNCTION >> bytecode that needs more than 800 traces operations, even after >> optimization :-). > > yes, I agree that translate.py is messy :-). > > Also, we have a speedup of ~2-2.5x which is more or less what you would expect > by "just" removing the interpretation overhead. It probably indicates that we > have laaaarge room for improvements, but I suppose that we already knew that > :-) >
[citation needed] I think 2x comes from 1999 or so. It must be benchmarked again to prove that. I think there are various clues that this number has changed (even maybe dropped) _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
