1711223 - 2.02 - 2.02% Base Content Heap Unclassified / Base Content Heap Unclassified (Linux) regression on Wed May 12 2021

Status: RESOLVED WONTFIX

(Core :: DOM: Content Processes, defect)

Description

[Andra Esanu (needinfo me)]

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

Regressions:

Ratio	Suite	Test	Platform	Options	Absolute values (old vs new)
2%	Base Content Heap Unclassified		linux1804-64-shippable		3,507,344.00 -> 3,578,048.67
2%	Base Content Heap Unclassified		linux1804-64-shippable		3,507,623.33 -> 3,578,591.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 offending patch(es) will be backed out in accordance with our regression policy.

For more information on performance sheriffing please see our FAQ.

Comment 1

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

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

Comment 2

[Sean Feng [:sefeng]]

I don't think we need to worry about this one. It makes sense as we've started to initiliazed NSS earlier, so the memory allocation of NSS also started to happen earlier.

I think we can just close this bug.

Comment 3

[Andrew McCreight [:mccr8]]

How often is NSS actually initialized in a content process?

Anyways, this is an intentional regression, and hopefully doesn't have any real effect most of the time.

Comment 4

[Sean Feng [:sefeng]]

It was very frequent based on the profiles that we have seen.