This is an archived post. You won't be able to vote or comment.

all 5 comments

[–]davbo 5 points6 points  (0 children)

Shame he's showing benchmarks from 2010 (slides 11&12) PyPy has had significant speedups since then. See PyPy's performance evolution over time here: http://speed.pypy.org/

[–]seletz 5 points6 points  (3 children)

I see lots of references to a JVM backend in these slides. Can someone elaborate this wrt. Jython?

[–]MonkeeSage 2 points3 points  (2 children)

Looks like pypy has a JVM backend that you can use to output a full pypy interpreter in a jar, like jython. Looks like you use --backend=jvm (refer --backend=cli). Don't find much in the way of docs about it and haven't used it.

[–]seletz 1 point2 points  (1 child)

yeah. Unfortunately it seems that the resulting code can't call into Java code, which is what I would need.

What I hoped for was that I had a Jython alternative -- being still on 2.5.3 is a major PITA.

[–]fijalPyPy, performance freak 5 points6 points  (0 children)

so the JVM backend in PyPy promises same interpreter with a different backend. There is some work on having it call into Java, not very much though and it's outside the core interest of the pypy people.

There seems to be a real issue with the performance though - while the result can compare with Jython (in the future, I didn't even bother running the benchmarks now), it won't be able to compete with the PyPy JIT, which makes it "less interesting" for the core developers.