1385960 - 2.48 - 24.63% tp5o_webext % Processor Time / tp5o_webext Private Bytes (windows7-32) regression on push 807acedaf25de607e78ef55453cef1a5e25e183c (Mon Jul 31 2017)

Status: RESOLVED WONTFIX

(Testing :: Talos, defect)

Description

[William Lachance (:wlach)]

Hey Tarek, it looks like your change in bug 1384137 caused the talos numbers to change. I'm guessing this is just an artifact of your harness change somehow, but just wanted to file a bug to track. If you're ok with this change (i.e. understand why it occurred and are ok with the new baseline), please feel free to resolve as wontfix.

--

Talos has detected a Firefox performance regression from push:

https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=807acedaf25de607e78ef55453cef1a5e25e183c

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

Regressions:

 25%  tp5o_webext % Processor Time windows7-32 opt e10s     44.63 -> 55.62
  2%  tp5o_webext Private Bytes windows7-32 opt e10s        143,983,912.87 -> 147,560,794.85


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

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

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

I am always confused how changing we ended up with regressions by changing the way we install addons.  In this case we are not using marionette, so I think the browser is behaving differently- although -marionette was only used in the profile creation- and it isn't clear what lingering effect it would have on the profile on next reboot.

I will say that now we are running both the webextension test and the non webext version in the same fashion, so this change is making us test the right things.

I will see if :tarek has other thoughts or ideas here before resolving this as wontfix.

Comment 2

[Tarek Ziadé (:tarek)]

Yes, I am not sure why it's impacting performances. I defer it to Joel