Closed
Bug 1461934
Opened 7 years ago
Closed 7 years ago
0.17 - 0.27% installer size (osx-cross, windows2012-32, windows2012-64) regression on push c82274a23aeaa6be8b7509de05822cb4bfa7729e (Tue May 15 2018)
Categories
(Core :: MFBT, defect)
Core
MFBT
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: igoldan, Unassigned)
References
Details
(Keywords: regression)
We have detected a build metrics regression from push:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?changeset=c82274a23aeaa6be8b7509de05822cb4bfa7729e
As author of one of the patches included in that push, we need your help to address this regression.
Regressions:
>100KBytes installer size windows2012-64 pgo 60,106,830.04 -> 60,270,100.17
>100KBytes installer size windows2012-32 pgo 55,748,191.17 -> 55,884,320.25
>100KBytes installer size osx-cross opt 66,311,093.17 -> 66,427,095.92
You can find links to graphs and comparison views for each of the above tests at: https://treeherder.mozilla.org/perf.html#/alerts?id=13232
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
Reporter | ||
Updated•7 years ago
|
Component: Untriaged → MFBT
Product: Firefox → Core
Reporter | ||
Comment 1•7 years ago
|
||
:froydnj Bug 1410186 caused an increase in installer size. Can we lessen this or should we just accept the increase?
Flags: needinfo?(nfroyd)
Comment 2•7 years ago
|
||
(In reply to Ionuț Goldan [:igoldan], Performance Sheriffing from comment #1)
> Can we lessen this or should we just accept the increase?
There's not much we can do that we haven't already done, and this is a Nightly/early Beta only increase.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(nfroyd)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•