Monday, January 25, 2010

In the past few months, we made tremendous progress on the JIT front.
To monitor the progress daily, we introduced recently some cool graphs
that plot revision vs performance. They are based on unladen swallow
benchmark runner and they're written entirely in JavaScript, using canvas
via the JQuery and Flot libraries.
It's amazing what you can do in JavaScript these days... They are also
tested via the very good oejskit plugin, that integrates py.test
with JavaScript testing, driven by the command line.

As you can probably see, we're very good on some benchmarks and not that
great on others. Some of the bad results come from the fact that while we
did a lot of JIT-related work, other PyPy parts did not see that much
love. Some of our algorithms on the builtin data types are inferior to those
of CPython. This is going to be an ongoing focus for a while.

We want to first improve on the benchmarks for a couple
of weeks before doing a release to gather further feedback.

Cheers,
fijal

Hello.

In the past few months, we made tremendous progress on the JIT front.
To monitor the progress daily, we introduced recently some cool graphs
that plot revision vs performance. They are based on unladen swallow
benchmark runner and they're written entirely in JavaScript, using canvas
via the JQuery and Flot libraries.
It's amazing what you can do in JavaScript these days... They are also
tested via the very good oejskit plugin, that integrates py.test
with JavaScript testing, driven by the command line.

As you can probably see, we're very good on some benchmarks and not that
great on others. Some of the bad results come from the fact that while we
did a lot of JIT-related work, other PyPy parts did not see that much
love. Some of our algorithms on the builtin data types are inferior to those
of CPython. This is going to be an ongoing focus for a while.

We want to first improve on the benchmarks for a couple
of weeks before doing a release to gather further feedback.