Closed Bug 1383103 Opened 2 years ago Closed 2 years ago

2.98% tsvgr_opacity (linux64) regression on push 26a9c5a88cc3f204fcc94e71bb4a1fca02e3207a (Thu Jul 20 2017)


(Firefox :: Theme, defect)

53 Branch
Not set





(Reporter: jmaher, Unassigned)



(Keywords: perf, regression, talos-regression)

Talos has detected a Firefox performance regression from push:

As author of one of the patches included in that push, we need your help to address this regression.


  3%  tsvgr_opacity summary linux64 pgo e10s     326.07 -> 335.78

You can find links to graphs and comparison views for each of the above tests at:

On the page above you can see an alert for each affected platform as well as a link to a graph showing the history of scores for this test. There is also a link to a treeherder page showing the Talos jobs in a pushlog format.

To learn more about the regressing test(s), please see:

For information on reproducing and debugging the regression, either on try or locally, see:

*** Please let us know your plans within 3 business days, or the offending patch(es) will be backed out! ***

Our wiki page outlines the common responses and expectations:
as a note, this is pgo only, we do not see this on opt.

::dao, would you have any ideas why this test might regress after your push?
Flags: needinfo?(dao+bmo)
The change itself seems innocent, i.e. changing the border radius from 2px to 4px shouldn't be /significantly/ more expensive. But any change in the primary UI will naturally affect the PGO profile causing different areas of code to get optimized. We can't control this directly.
Flags: needinfo?(dao+bmo)
ok lets marks this as wontfix!
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.