Hi Laura, you bring up good points, however, it is not as straight forward as it seems.

I see, under a section called 'latest results' a list of all the recent times when we became slower.  It's thus a 'recent problems' page -- we have actually improved in recent times in many areas, and nowhere is that shown.

Well, it really is a list of the latest results. The problem is that speed.pypy.org is foremost a tool to help in development. As such, the logic behind the "latest results" list is regression oriented, or let us say pessimistic. For example, this revision: http://speed.pypy.org/changes/?rev=42312:392bbf936179 The average change is actually -0.91%, which is actually an improvement, though not an statistical significant one. However, There was a sizeable regression in spitfire_cstringio, +5.21. The "summary" for that revision is then "regression for an individual benchmark". Which is actually what developers need to know: they should check whether that revision really introduced a real regression in performance. Now, it is true that since that new main page was introduced the impression it has given is one of regressions, mostly. But if you look at all the graphs together 8http://speed.pypy.org/timeline), you see that in the last weeks there has been a slight upwards (worse performance) trend in many benchmarks. So I think Codespeed has done the right thing! Note that a week ago I did up the threshold from 3% to 4% changes That said, I do understand where you are coming from. I would point outsiders though directly to http://speed.pypy.org/comparison/ So what can some body think about what could be changed or added so that the main page doesn't give a negative impression to the non-developer? Something I could think of is to add, above the results list, a plot showing the overall trend over the last 2 or 3 months. What do you think?

The other thing I want is for the graphs you get, for instance with http://speed.pypy.org/changes/?rev=42312:392bbf936179&exe=%203&env=tannit to have, in addition to the selection button beside: 'result for revision' an actual label that says 'build 42312:392b' or something that you can select with your mouse and use to paste into things like this mail article.

I think to the right of the changes table there is a box with info for the revision, with a text field you can select and copy. Isn't that what you want?

article.  It would also be useful to label the run with something more meaningful than 'tannit' for outsiders -- 64 bit ubuntu linux  for instance.

Agreed. I would also rather call the machines/environments like that. 2011/2/27 Laura Creighton <lac@openend.se>:

<Resend.  I seem to have typed python-dev@codespeak.net last time.  sorry Miguel.>

I'd like to change what is displayed on the speed.python.org frontpage. Right now, as I look at http://speed.pypy.org/  I see, under a section called 'latest results' a list of all the recent times when we became slower.  It's thus a 'recent problems' page -- we have actually improved in recent times in many areas, and nowhere is that shown.  As we go off to PyCON, which is March 9-17, I intend to mention how great PyPy is, and that you can see it for yourself at speed.pypy.org.  Thus, without lying, I would like it if the first impression of PyPy's speed that people got when looking at the site was 'we're getting faster'.  Do you think you could change the front page so that what was displayed was more balanced with respect to good news and bad news?

I realise that there is nothing you can do if we make a recent build that slows everything down, but for instance in build 42312:392b (Feb 26) we have improvments which are not shown on the main page.  I actually think that the _trend_  is a more useful thing to display on the front page, though that might be because it is so green right now. :-)

The other thing I want is for the graphs you get, for instance with http://speed.pypy.org/changes/?rev=42312:392bbf936179&exe=%203&env=tannit to have, in addition to the selection button beside: 'result for revision' an actual label that says 'build 42312:392b' or something that you can select with your mouse and use to paste into things like this mail article.  It would also be useful to label the run with something more meaningful than 'tannit' for outsiders -- 64 bit ubuntu linux  for instance.

Thanks very much, Laura Creighton