1403464 - 16.12 - 27.05% tabpaint / tp5n nonmain_startup_fileio (windows10-64, windows7-32) regression on push 23e5c31fbaea0c266192851efb029d443f3cf895 (Tue Sep 26 2017)

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?changeset=23e5c31fbaea0c266192851efb029d443f3cf895

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

Regressions:

 27%  tp5n nonmain_startup_fileio windows7-32 pgo e10s     1,593,567.42 -> 2,024,643.33
 18%  tabpaint summary windows10-64 pgo e10s               58.25 -> 68.79
 17%  tabpaint summary windows7-32 opt e10s                68.16 -> 80.00
 16%  tabpaint summary windows10-64 opt e10s               63.72 -> 74.00


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

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]]

Were these expected or should these be the new baselines?

Comment 2

[Joel Maher ( :jmaher ) (UTC -8)]

yes, the xperf is because we are not using a .xpi (.zip) file, but instead the raw files for the addons- tabpaint is funny- this appears to be because there were changes made to tabpaint, but we never updated the addon- this resulted in testing older code.