Way back when, (almost exactly a year ago, actually) I built a dashboard for getting at-a-glance views of our performance metrics, to make it easier to spot regressions and assess the state of the tree.
And so, of course, days later we decommissioned those boxes and that whole way of reporting performance, and the dashboard fell into disrepair.
A couple days ago I rebuilt it.
It’s in its infancy right now. It only pulls data for the 1.9.1/Firefox3.1 branch, and it only pulls a couple tests thus far, but those are easy to add. It has no fun widgets or user-preference memory or any of that, but patches are accepted.
The code is in a public hg repo here in case you want to beat me to any particular feature. To run your own copy, just clone the repo, run the scrapedata.py script to get some up to date stats, and then open index.html in a suitably awesome browser.
The graphs are built with google’s really excellent charting API. It’s reasonably flexible, and great for quick stuff BUT I’m not looking to replace our existing graph server. That thing has all kinds of charting goodness that I absolutely don’t aim to reinvent.
This is a quick, dumb dashboard; not an immersive data navigation environment. It isn’t complicated, it’s just something I thought would be useful. How would you make it better?
I find the dashboard a lot easier to read than the graph server.
This could be some kind of “graph server lite”. Fast loading, with the most important information right at your fingertips. Anyone who wants the gory details can use the full-fletched graph server.
This is quite excellent.
Have you seen http://build.chromium.org/buildbot/perf/dashboard/overview.html ? The “baseline” thing they do is nice.
What I find impressing on the chromium side is that they actually show error bars.
I wonder if the piecewise-linear graphs are easier to read than piecewise-constant would be. The latter are closer to the real life, for sure.
Well this is just awesome
The good resource is informative and actual