1939879 - 2.56 - 0.96% Resident Memory Fresh start [+30s] / Explicit Memory Fresh start [+30s] + 2 more (Windows) regression on Tue November 19 2024

Status: RESOLVED WONTFIX

(Core :: Audio/Video: Playback, defect)

Description

[Treeherder Bug Filer]

Perfherder has detected a awsy performance regression from push 742621410f46febbaeb897b2ad32582dc39cf689. 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)
3%	Resident Memory Fresh start [+30s]	windows11-64-2009-shippable-qr	fission tp6	329,280,853.33 -> 337,706,325.33
2%	Heap Unclassified Fresh start [+30s]	windows11-64-2009-shippable-qr	fission tp6	34,760,312.33 -> 35,483,525.33
1%	Explicit Memory Fresh start	windows11-64-2009-shippable-qr	fission tp6	220,419,066.67 -> 222,681,184.00
1%	Explicit Memory Fresh start [+30s]	windows11-64-2009-shippable-qr	fission tp6	178,636,940.00 -> 180,344,565.33

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 43243

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

[BugBot [:suhaib / :marco]]

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

Comment 2

[Andrew Osmond [:aosmond] (he/him)]

We expected some additional footprint from prestarting the RDD process