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

Regressions:

8% tp5o responsiveness windows7-32-shippable opt e10s stylo 1.00 -> 1.08
3% tp5o responsiveness windows7-32-shippable opt e10s stylo 1.04 -> 1.07

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.

The patch changes our memory allocation layout, so it's normal that we're seeing some random performance fluctuations. This is explained in the bug itself: https://bugzilla.mozilla.org/show_bug.cgi?id=1553717#c15 and https://bugzilla.mozilla.org/show_bug.cgi?id=1553717#c0.

Given that this is a small regression in one subtest on one platform, I'd say we don't care.

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

Closing old win7 regressions