I'm all for smaller is better in the evolution plot
Seems more rational
except you can't call it "performance" in the header above the plot then.
On 18 March 2011 00:23, Miquel Torres wrote:
> Oh! it just downed on me that there is a very easy way to do a "bigger
> is better" plot without changing any of the current views of plots.
>
> The "How has PyPy performance evolved over time?" plot, with
> represents the geometric average of all normalized benchmarks. You may
> have noticed the number inside parenthesis, which it is precisely the
> inverse.
>
> That one plot can thus be easily inverted, to be able to show "times
> faster than", without changing the rest of the site.
>
>
>
> 2011/3/18 Miquel Torres :
>> I understand what you say, and it is certainly possible to turn
>> benchmarks into "bigger is better". As Laura wrote though, it is only
>> natural to measure time, because that is what you actually what to do:
>> reduce the time it takes to complete some task.
>>
>> Other projects do the same. See for example jQuery announcing a newer,
>> faster release: http://blog.jquery.com/2010/10/16/jquery-143-released/
>>
>> (scroll down for lots of performance plots)
>>
>> *However*, it seems that for the last release they have done what you
>> propose: http://blog.jquery.com/2011/01/31/jquery-15-released/
>>
>> They have changed the units from "seconds" to number of "iterations per
>> second".
>>
>> In any case that is something for the PyPy developers to decide.
>>
>> Cheers,
>> Miquel
>>
>>
>> 2011/3/17 Laura Creighton :
>>>
>>> Smaller is better when you are dieting. Or when you are racing.
>>> Given that there is talk that we will measure memory size as well, and
>>> turn into performance.pypy.org then I think that the 'smaller is
>>> better' idea will be well understood. As a practical matter, making
>>> 'faster' be 'bigger' doesn't make sense in terms of benchmarks, in which
>>> you want to be the first to finish.
>>>
>>> Laura
>>>
>>> ___
>>> 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
