Hi Jacob, benchmark descriptions is certainly something that could be improved upon. As exarkun said, a quick way to get *something* is to just fill out the description fields for each benchmark. I can happily do that, I just need a mail containing a list with brief descriptions for all the benchmarks ;-) I can even imaging improving it further so that there is a link to source code (your point 4) or even an info page dedicated to each benchmark. Points 2 and 3, as Maciej said, is problematic. Reasons why it performs better or worse than cpython and how it could be improved is something that may change fairly often for some benchmarks, which would be a pain to maintain. And speed.pypy.org doesn't have 3 or 4 benchmarks, it has 25 right now! @Andy: memory consumption is difficult to measure. I think someone was looking at how to best measure it? Cheers, Miquel 2010/12/4 Andy <angelflow@yahoo.com>:

The one thing that would be the most helpful is that for each test shows the memory usage comparison between PyPy-JIT & CPython.

--- On Fri, 12/3/10, Jacob Hallén <jacob@openend.se> wrote:

...

From: Jacob Hallén <jacob@openend.se> Subject: [pypy-dev] Idea for speed.pypy.org To: pypy-dev@codespeak.net Date: Friday, December 3, 2010, 6:42 PM Something that would be nice on the speed.pypy.org site would be that each benchmark links to a page that describes the benchmark

- What the benchmark is designed to measure - Why PyPy performs better/worse than CPYthon (if known) - What might be done to further improve performance (if there are ideas) - Link to the source code of the benchmark

Any takers?

Jacob

-----Inline Attachment Follows-----

_______________________________________________ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev

_______________________________________________ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev