Open Bug 1949430 Opened 8 months ago Updated 8 months ago

[meta] Beta 136 Performance changes when we unset EARLY_BETA_OR_EARLIER

Categories

(Testing :: Performance, defect)

Firefox 123
defect

Tracking

(firefox137 affected)

Tracking Status
firefox137 --- affected

People

(Reporter: fbilt, Unassigned)

References

Details

(Keywords: meta, perf, perf-alert)

Perfherder has detected a build_metrics performance change from push 1e770e78f33e7f6e62be3662eace6c88aa012620.

Improvements:

Ratio Test Platform Options Absolute values (old vs new)
1% installer size osx-shippable nightly 93,416,599.17 -> 92,728,196.83
1% installer size windows2012-64-devedition nightly 105,169,709.88 -> 104,398,106.50
1% installer size windows2012-64-shippable nightly 105,047,662.08 -> 104,294,237.67
1% installer size linux32-devedition nightly 76,229,220.00 -> 75,686,224.00
1% installer size osx-cross-devedition nightly 102,791,025.58 -> 102,059,120.42
... ... ... ... ...
1% installer size windows2012-aarch64-devedition nightly 95,744,700.33 -> 95,168,486.75

Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests.

If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a sheriff to do that for you.

You can run these tests on try with ./mach try perf --alert 43918

For more information on performance sheriffing please see our FAQ.

:fbilt, since this bug is a regression, could you fill (if possible) the regressed_by field?
For more information, please visit BugBot documentation.

Flags: needinfo?(fbilt)

This bug has been marked as a regression. Setting status flag for Nightly to affected.

Flags: needinfo?(fbilt)
Keywords: regressionmeta
Summary: Beta 136 Performance changes when we unset EARLY_BETA_OR_EARLIER → [meta] Beta 136 Performance changes when we unset EARLY_BETA_OR_EARLIER
You need to log in before you can comment on or make changes to this bug.