Open Bug 1641623 Opened 4 years ago Updated 2 years ago

Add a numerical summary of Perfherder improvement/regression to the Compare Revisions view


(Tree Management :: Perfherder, enhancement, P3)



(Not tracked)


(Reporter: acreskey, Unassigned)


(Blocks 1 open bug)


This bug is to discuss adding one or more numerical summaries to the Perfherder Compare Revisions view

When comparing the performance of different revisions against each other, the performance team has found it to be quite useful to look at an "overall number" for each metric.

For instance, in large-scale local pageload tests, we will look at the geomean of improvements, over a wide range of sites, for a given metric (e.g. load event).

An example can be seen here:

In this case, we see that this build of Fenix showed a ~31.42% overall improvement in pageload time relative to the baseline build.

We've found these summaries to be numerical quite stable - even if per-site results vary significantly, the overall improvements are consistently reproducible within a ~1-2% range.

I propose adding a similar calculated result to Perfherder Compare Revision views such as this one:

Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.