Closed
Bug 1503789
Opened 6 years ago
Closed 6 years ago
0.2 - 0.23% installer size (osx-cross, windows2012-32, windows2012-64) regression on push 25aa97e7d1062b21a84f3acb950859de09f40533 (Wed Oct 31 2018)
Categories
(Core :: Graphics: ImageLib, defect, P3)
Tracking
()
RESOLVED
WONTFIX
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=25aa97e7d1062b21a84f3acb950859de09f40533
As author of one of the patches included in that push, we need your help to address this regression.
Regressions:
~150KBytes installer size windows2012-64 pgo 67,567,861.75 -> 67,721,447.42
~150KBytes installer size osx-cross opt 73,756,408.62 -> 73,922,256.50
>100KBytes installer size windows2012-32 pgo 64,579,063.50 -> 64,710,223.17
You can find links to graphs and comparison views for each of the above tests at: https://treeherder.mozilla.org/perf.html#/alerts?id=17295
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•6 years ago
|
Component: General → ImageLib
Product: Testing → Core
Reporter | ||
Comment 1•6 years ago
|
||
Is there something we can do to dim down this binary increase?
Flags: needinfo?(aosmond)
Comment 2•6 years ago
|
||
It's a new video codec, so this increment it's expected.
Comment 3•6 years ago
|
||
I don't think there is anything we can do. I already trimmed the library down by only including files we needed, and left out bits like the encoder.
Flags: needinfo?(aosmond)
Updated•6 years ago
|
Priority: -- → P3
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•