1911532 - 6.82 - 2.8% speedometer AngularJS-TodoMVC/DeletingAllItems/Async / speedometer Elm-TodoMVC/CompletingAllItems + 3 more (Linux, Windows) regression on Tue July 30 2024

Status: RESOLVED WORKSFORME

(Core :: JavaScript: GC, defect)

Description

[Treeherder Bug Filer]

Perfherder has detected a browsertime performance regression from push e6032899a5ab8e585861e141a41ce4000c4aa039. 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)	Performance Profiles
7%	speedometer AngularJS-TodoMVC/DeletingAllItems/Async	windows11-64-nightlyasrelease-qr	fission webrender	2.78 -> 2.97	Before/After
6%	speedometer AngularJS-TodoMVC/DeletingAllItems/Async	windows11-64-nightlyasrelease-qr	fission webrender	2.79 -> 2.94	Before/After
5%	speedometer AngularJS-TodoMVC/DeletingAllItems/Sync	linux1804-64-shippable-qr	fission webrender	112.60 -> 118.52	Before/After
5%	speedometer AngularJS-TodoMVC/DeletingAllItems	linux1804-64-shippable-qr	fission webrender	117.35 -> 123.20	Before/After
3%	speedometer Elm-TodoMVC/CompletingAllItems	windows11-64-nightlyasrelease-qr	fission webrender	37.58 -> 38.64	Before/After

Improvements:

Ratio	Test	Platform	Options	Absolute values (old vs new)	Performance Profiles
3%	speedometer EmberJS-Debug-TodoMVC/DeletingItems	macosx1400-64-shippable-qr	fission webrender	59.61 -> 57.69	Before/After
3%	speedometer EmberJS-Debug-TodoMVC/DeletingItems/Sync	macosx1400-64-shippable-qr	fission webrender	59.24 -> 57.36	Before/After
3%	speedometer EmberJS-Debug-TodoMVC/CompletingAllItems/Sync	windows11-64-shippable-qr	fission webrender	99.44 -> 96.72	Before/After
3%	speedometer EmberJS-Debug-TodoMVC/CompletingAllItems	windows11-64-shippable-qr	fission webrender	101.40 -> 98.65	Before/After

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.

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 1592

For more information on performance sheriffing please see our FAQ.

Comment 1

[Jan de Mooij [:jandem]]

This is mostly the inverse of the improvements/regressions reported in bug 1910420. See for example these graphs:

https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,3925531,1,13
https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,5042023,1,13

I'll close this as duplicate of that bug and I'm still looking into that one.

Comment 2

[Florin Bilt]

Hello Jan,
Considering the metrics reported in this bug are the inverse of the bug you mentioned, why did you close this bug as duplicate ?

Comment 3

[Jan de Mooij [:jandem]]

(In reply to Florin Bilt from comment #2)

Hello Jan,
Considering the metrics reported in this bug are the inverse of the bug you mentioned, why did you close this bug as duplicate ?

I was thinking of it as a single cluster of related bugs, but feel free to change the status if you think something else is more appropriate.

Comment 4

[Florin Bilt]

Hi Jan
Could you please close this bugs (Bug 1911532 and bug 1910420) and let me know when they have been fixed?
Thank you.

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

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

Comment 6

[Jan de Mooij [:jandem]]

Closing as most of this was reverting regressions/improvements reported in bug 1910420 after bug 1910544 landed.