For Stylo and Hasal (and probably other things as well), we want to be able to compare a "base" version of Firefox to an alternate version (Firefox w/ stylo enabled for stylo, Chrome for Hasal), to see how the performance compares over time. We should generalize the existing e10s dashboard code (which has already had a fair amount of work sunk into it) for this purpose. I believe all we should need to do is make the "test options" a parameter passed in to the "dashboard" components. Doing this should make bugs 1288857 and 1314223 trivial.

Hi Robert, could you help to let us know the status? As a Hasal demo in Hawaii, we would like to have the page to compare result between 2 versions. is it possible to help on this? Many thanks.

(In reply to Bobby Chien [:bchien] from comment #1) > Hi Robert, could you help to let us know the status? As a Hasal demo in > Hawaii, we would like to have the page to compare result between 2 versions. > is it possible to help on this? Many thanks. I plan to make good progress on this (generalizing the e10s dashboard code) over the next couple of weeks.

Comment on attachment 8811805 [details] [treeherder] rwood-moz:bug1314317 > mozilla:master Messed up my PR when trying to rebase and fix a conflict, will open a new PR.

Comment on attachment 8812324 [details] [treeherder] rwood-moz:rwood-bug1314317 > mozilla:master Carrying-forward the R+ from :wlach as this PR is exactly the same as the last just with minor improvements as suggested.

Commit pushed to master at https://github.com/mozilla/treeherder https://github.com/mozilla/treeherder/commit/4bee8f1702ca20349ad3dc52743bce155fb0acb8 Bug 1314317 - Generalize e10s dashboard to prepare for future comparisons (#1986)