1483990 - 72.22 - 93.03% build times (android-4-0-armv7-api16, android-4-2-x86) regression on push 19f9ed0f53b917f064655375341db76a9c5a4461 (Tue Aug 14 2018)

Status: RESOLVED WONTFIX

(Firefox Build System :: General, defect)

Description

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

We have detected a build metrics regression from push:

https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?changeset=19f9ed0f53b917f064655375341db76a9c5a4461

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

Regressions:

 93%  build times android-4-0-armv7-api16 opt taskcluster-m4.2xlarge     1,013.79 -> 1,956.89
 72%  build times android-4-2-x86 opt taskcluster-m5.4xlarge             530.96 -> 914.43


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

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 jobs in a pushlog format.

To learn more about the regressing test(s), please see: https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Automated_Performance_Testing_and_Sheriffing/Build_Metrics

Comment 1

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

this is hard to tell if the real culprit is bug 1480006, or not- it is the most likely suspect and in common in most of the ranges.  Since we build on so many different types of machines, the signal we get is broken up.

:glandium, does it seem reasonable that your change from bug 1480006 would cause a large regression in build time for android?

Comment 2

[Mike Hommey [:glandium]]

Yes, it's expected. LTO means more optimization, and that takes time. We should have seen talos perf improvements as well.

Comment 3

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

we don't have any android perf tests at the moment, possibly next week a few will get turned on.