1927688 - 3.5% speedometer BackboneJS-TodoMVC/CompletingAllItems/Async (OSX) regression on Thu October 24 2024

Status: RESOLVED INVALID

(Core :: Performance: General, defect)

Description

[Treeherder Bug Filer]

Perfherder has detected a browsertime performance regression from push 8db300296a58df2a544398079732a76484ad111f. 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
4%	speedometer BackboneJS-TodoMVC/CompletingAllItems/Async	macosx1015-64-shippable-qr	fission webrender	3.62 -> 3.75	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 all of these tests on try with ./mach try perf --alert 2735

The following documentation link provides more information about this command.

For more information on performance sheriffing please see our FAQ.

If you have any questions, please do not hesitate to reach out to [e-mail].

Comment 1

[Donal Meehan [:dmeehan]]

:ahochheiden:glandium/ pinging as Triage Owner and reviewer of the regressing patch.
afaik :padenot is on PTO. Next week is the final week of beta for Fx133. Could you please take a look at this, if there's anything concerning?

Comment 2

[Mike Hommey [:glandium]]

The graph doesn't definitely point to 8db300296a58df2a544398079732a76484ad111f, and 8db300296a58df2a544398079732a76484ad111f can't really cause a performance regression, so this would have to be something else.

Comment 3

[Donal Meehan [:dmeehan]]

:fdoty could this be triaged?
Looking at the graph over 90 days, it looks like there were different spikes of performance issues between Oct 20 and Oct 27.
However, now the graph seems the same as before.
This bug should possible be resolved?

Comment 4

[Florin Bilt]

I closed this alert, seems invalid because in the period around Octomber 8th, we had the same range of values as we have now.
You can close this ticket as invalid