On 08/15/2012 07:08 PM, Gregory Szorc wrote:
When I was working on this project last year, I designed a build charts
view to help visualize which parts were taking the longest (you can see
implicit dependencies between build/test tasks by seeing when certain
jobs run), which proved very helpful to determine which areas we needed
to optimize:
http://brasstacks.mozilla.com/gofaster/#/buildcharts
Very nice. If you are accepting feature requests, I think the most
helpful would be checkboxes to filter hardware platforms. It's kind of
hard sorting through everything when all the platforms are mixed together.
We have a bugzilla component for filing these sorts of things (though
note that AFAIK no one's actively working on the dashboard atm):
https://bugzilla.mozilla.org/enter_bug.cgi?component=GoFaster&product=Testing
I do agree that more filtering options would be useful. I think the
first thing to do would be to confirm the data in these charts is valid
though.
I would also like to see hardware utilization in this chart somehow. If
a build step is consuming all local hardware resources (mainly CPU and
I/O), that is a completely different optimization strategy from one
where we are not fully utilizing local capacity or are waiting on
external resources, such as those on a network.
I'm not sure if this works at all anymore, but it used to be that you
could click on a particular build to get the breakdown of the amount of
time spent on any particular step. We could certainly do a similar thing
with hardware utilization -- just a matter of getting the information
available somewhere we can access it (we used elastic search for the
build steps).
Will
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
