btw, benchmark game also tracks memory footprint, pypy is a little liberal here for small benchmarks, which there are many.
On 7 April 2011 10:15, Damon McCormick <damo...@gmail.com> wrote: > The benchmark game also compares on code size. So if PyPy provides better > performance with smaller code size (i.e. if allows you to write something in > the most concise, Pythonic way and get great performance), this may not show > up unless PyPy can run a different version of a benchmark that actually uses > less code. > (Disclaimer: it's been a few years since I looked at the benchmark game > Python programs. Maybe they're already written very concisely, in which > case this point is moot) > -Damon > > On Thu, Apr 7, 2011 at 12:51 AM, Vincent Legoll <vincent.leg...@gmail.com> > wrote: >> >> Hello, >> >> On Thu, Apr 7, 2011 at 5:52 AM, Maciej Fijalkowski <fij...@gmail.com> >> wrote: >> > It does make sense to compare CPython and >> > PyPy on the same set of benchmarks (actually that's what we do with >> > speed.pypy.org, we deliberately tried to avoid modifying benchmarks). >> >> But speed.pypy.org is about comparing cpython vs pypy, whereas >> the benchmark game compares a lot of quite different laguages, that >> is not exactly the same thing. So, that may warrant different rules... >> >> -- >> Vincent Legoll >> _______________________________________________ >> pypy-dev@codespeak.net >> http://codespeak.net/mailman/listinfo/pypy-dev > > > _______________________________________________ > pypy-dev@codespeak.net > http://codespeak.net/mailman/listinfo/pypy-dev > _______________________________________________ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev