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

Improvements:

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.

this improvement is generated eater by the backout of 1675207 or the other sync commits from the patch:

https://treeherder.mozilla.org/jobs?repo=autoland&group_state=expanded&selectedTaskRun=KKi792MMSHqsZyEStPwU3Q.0&searchStr=os%2Cx%2C10.14%2Cwebrender%2Cshippable%2Copt%2Cbrowsertime%2Cperformance%2Ctests%2Con%2Cfirefox%2Ctest-macosx1014-64-shippable-qr%2Fopt-browsertime-tp6-firefox-twitter-e10s%2Ctwitter&revision=997d2fc150eea16afad461475fbcbcd582558a52

looking at the historical data this looks similar to the regression Bug 1681030 . Are the sync changes related with wayland feature?

I think bug 1675207 should have nothing to do with this.
After the push 2d192d43277bb6231b9145572d0059c5964f9d96, the patch in bug 1675207 was landed back in 3389a00741138b4c0d34ca9fb6bbb2860e743f0c. According to this graph, it seems that the push 2d192d43277bb6231b9145572d0059c5964f9d96 (without the patch in bug 1675207) and 3389a00741138b4c0d34ca9fb6bbb2860e743f0c (with the patch) have the same result.

In addition, bug 1675207 is all about websocket and thus is not related to wayland feature.

Florin, could you confirm what I said above is correct? Thanks.

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

IIUC the patches should have nothing to do with each other.

FTR.: I found the underlying issue of bug 1681030, so we could revisit this once the fixes land (see also bug 1645528 comment 76)