1481835 - 29.86 - 78.14% tsvg_static (linux64, linux64-qr, osx-10-10) regression on push 73a02f476951 (Tue Aug 7 2018)

Status: RESOLVED WONTFIX

(Testing :: Talos, defect)

Description

[Ionuț Goldan [:igoldan]]

Talos has detected a Firefox performance regression from push:

https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=4dcd86b7c22d0ed45bd616c159ef343ef641a74a&tochange=73a02f4769511bd6a1afc433de4450ca8b718868

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

Regressions:

 78%  tsvg_static osx-10-10 opt e10s stylo     46.15 -> 82.22
 35%  tsvg_static linux64 pgo e10s stylo       49.62 -> 67.00
 33%  tsvg_static linux64 opt e10s stylo       50.61 -> 67.30
 30%  tsvg_static linux64-qr opt e10s stylo    56.66 -> 73.58

Improvements:

 26%  tsvg_static windows10-64 pgo e10s stylo     48.42 -> 35.78
 21%  tsvg_static windows10-64 opt e10s stylo     47.21 -> 37.14


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

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

[Ionuț Goldan [:igoldan]]

:jwatt this is just a harness update and I would resolve this bug as WONTFIX, unless you think there's something wrong with the results.

Comment 2

[Jonathan Watt [:jwatt]]

Yes, this is expected. Fixing the test make it actually display the image it should be displaying, which naturally adds more overhead and causes it to take longer to complete. :)