On Fri, Oct 02, 2009 at 18:49 -0300, Leonardo Santagada wrote:
On Oct 2, 2009, at 5:20 PM, Stefan Behnel wrote:
Anders Hammarquist wrote:
Anyway, what I was thinking about, and need input on, is how to get at the interpreters to run the benchmark. [...]
I wonder, would it be possible to add Cython to the benchmark loop? I would love to see it compared to PyPy, simply because both projects aim to compile Python code to C code (amongst other things, obviously).
I know that Cython can't currently compete with PyPy in terms of feature completeness - it clearly lacks some very important features of the Python language, so it won't be able to run all benchmarks for a while, and the comparison would easily show where the black spots are that need fixing.
I think you did some really interesting experiments but the projects don't aim at the same thing at all. PyPy python interpreter is not compiling python code to C it is just interpreting it and using a jit to dynamically compile code (and this is directly to machine code). PyPy python interpreter is meant to be a fully compatible python interpreter and it doesn't depend on no CPython code (like cython does).
I am sure Stefan is fully aware of what PyPy is.
I only think it is interesting to compare pypy to other python interpreters, anything that fully suports the python language. I do find cython cool, but as it doesn't try to be a python interpreter there would be no point in doing that.
What I would like to see is comparisons against python 2.5-7, 3.1, unladen swallow, psyco 2.0 and ironpython.
sure, and Jython. I don't see harm in adding Cython for the benchmarks it understands and if it's all easy enough. But let's first get started to automatically benchmark pypy trunk/selected branches over the revisions and compare it to one or multiple CPython versions. best, holger