1477916 - 19.32% glterrain (windows10-64-qr) regression on push 5e2c3f2fb8a0 (Thu Jul 19 2018)

Status: RESOLVED DUPLICATE of bug 1416645

(Core :: Graphics: CanvasWebGL, defect)

Description

[Ionuț Goldan [:igoldan]]

Talos has detected a Firefox performance regression from push:

https://hg.mozilla.org/integration/autoland/rev/5e2c3f2fb8a0

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

Regressions:

 19%  glterrain windows10-64-qr opt e10s stylo     1.63 -> 1.95

Improvements:

 37%  glterrain windows10-64 opt e10s stylo     1.34 -> 0.84
 36%  glterrain windows10-64 pgo e10s stylo     1.33 -> 0.85
 36%  glterrain windows7-32 pgo e10s stylo      1.39 -> 0.89


You can find links to graphs and comparison views for each of the above tests at: https://treeherder.mozilla.org/perf.html#/alerts?id=14467

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: https://wiki.mozilla.org/Buildbot/Talos/Tests

For information on reproducing and debugging the regression, either on try or locally, see: https://wiki.mozilla.org/Buildbot/Talos/Running

*** 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: https://wiki.mozilla.org/Buildbot/Talos/RegressionBugsHandling

Comment 1

[Darkspirit]

(In reply to Ionuț Goldan [:igoldan], Performance Sheriffing from comment #0)
> Regressions:
>  19%  glterrain windows10-64-qr opt e10s stylo     1.63 -> 1.95

vs. bug 1474595 comment 17

Comment 2

[Kelsey Gilbert [:jgilbert]]

Not sure what's going on with WR, but that work is happening in bug 1416645.

Comment 3

[Ionuț Goldan [:igoldan]]

(In reply to Jeff Gilbert [:jgilbert] from comment #2)
> Not sure what's going on with WR, but that work is happening in bug 1416645.

:jgilbert thanks for linking this.