[pypy-dev] Nightly Benchmarks

Anders Hammarquist iko at openend.se
Thu Oct 8 19:24:43 CEST 2009

In a message of Mon, 05 Oct 2009 23:04:16 +0200, Miquel Torres writes:
>There are a couple of things I want to discuss:
>- An extra table (class) may be needed to store the hardware the benchmark
>was run on. pypy will probably need to be tested on other architectures.

Keeping track of the architecture makes sense. Possibly it could go as
a field on the interpreter instead.

>- The interpreter table needs extra fields:
>    - revision: absolutely necessary

My original thoughts for the revision would be to put it on the Run,
but if you are going to add several different languages it probably
makes more sense to put it on the interpreter. This would be the
version number for released (non-PyPy) interpreters.

>    - tag: this is for 1.0, 1.1, beta, trunk, snapshot, or what ever. This
>is needed to know what pypy revisions to list in the web page that allows
>comparison to other python implementations (most importantly cpython).
>    - Furthermore: You state that compile options are not needed, that they
>would be different interpreters.
>I agree that we can have pypy-c, pypy-crl and pypy-c-jit (for example) as
>different interpreters. But things can get messy if we add garbage
>collectors and other options:

I think we misunderstood eachother on this one. I would certainly
add a field for it on the interpreter object, keeping it in the name
could quickly get messy. I thought you were talking about adding
compile options to the Run.


More information about the Pypy-dev mailing list