Closed Bug 1870079 Opened 1 year ago Closed 1 year ago

0.73 - 0.61% installer size / installer size + 1 more (OSX) regression on Sat December 9 2023

Categories

(Core :: Performance, defect)

defect

Tracking

()

RESOLVED WONTFIX
Performance Impact none
Tracking Status
firefox-esr115 --- unaffected
firefox120 --- unaffected
firefox121 --- unaffected
firefox122 --- wontfix
firefox123 --- wontfix

People

(Reporter: afinder, Unassigned)

References

(Regression)

Details

(Keywords: perf-alert, regression)

Perfherder has detected a build_metrics performance regression from push 5e7ca7b9c60d764540bfc20b243ffaa67dfbfaa9. As author of one of the patches included in that push, we need your help to address this regression.

Regressions:

Ratio Test Platform Options Absolute values (old vs new)
1% installer size osx-shippable nightly 89,479,045.00 -> 90,129,876.50
1% installer size osx-nightlyasrelease nightly nightly-as-release 87,659,840.50 -> 88,207,306.50
1% installer size osx-aarch64-shippable aarch64 nightly 85,161,157.12 -> 85,681,225.42

Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests. Please follow our guide to handling regression bugs and let us know your plans within 3 business days, or the patch(es) may be backed out in accordance with our regression policy.

For more information on performance sheriffing please see our FAQ.

Set release status flags based on info from the regressing bug 1867581

:mleclair, since you are the author of the regressor, bug 1867581, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Flags: needinfo?(mleclair)

Set release status flags based on info from the regressing bug 1867581

:fdoty could this be triaged for severity?

Flags: needinfo?(fdoty)
Severity: -- → S3
Flags: needinfo?(fdoty)
Performance Impact: --- → none
Severity: S3 → S4

This increase in size came from the PGO change I made to make sure the tests ran to completion. The performance team has agreed to the trade-off considering how these changes improved Speedometer 3 runtime.

Status: NEW → RESOLVED
Closed: 1 year ago
Flags: needinfo?(mleclair)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.