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

Regressions:

83% raptor-tp6-pinterest-firefox-cold fcp windows10-64-shippable opt 632.79 -> 1,156.58
37% raptor-tp6-pinterest-firefox-cold windows10-64-shippable opt 958.82 -> 1,308.95
10% raptor-tp6-twitch-firefox-cold fcp linux64-shippable-qr opt webrender 106.58 -> 117.08
5% raptor-tp6-yahoo-news-firefox-cold fcp linux64-shippable opt 841.46 -> 886.33
2% raptor-tp6-paypal-firefox-cold fcp windows10-64-shippable-qr opt webrender 829.58 -> 850.17
2% raptor-tp6-yahoo-news-firefox-cold fcp linux64-shippable opt 848.46 -> 864.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.

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

This is just a reversal of the gains in bug 1645746. Once a proper fix for bug 1652126 has landed, we can turn the feature back on.