3.71 - 4.65% tscrollx (windows7-32-shippable) regression on push fe3c79839a883fd37d818a2720e025df394e3cec (Wed April 15 2020)
Categories
(Core :: Security: Process Sandboxing, defect, P5)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox75 | --- | unaffected |
firefox76 | --- | unaffected |
firefox77 | --- | wontfix |
firefox78 | --- | wontfix |
People
(Reporter: alexandrui, Assigned: cmartin)
References
(Regression)
Details
(4 keywords)
Talos has detected a Firefox performance regression from push:
As author of one of the patches included in that push, we need your help to address this regression.
Regressions:
5% tscrollx windows7-32-shippable opt e10s stylo 0.70 -> 0.74
4% tscrollx windows7-32-shippable opt e10s stylo 0.70 -> 0.72
Because of some bustages the tests didn't run on this push so we did a bisection whose result you can find here: bisection result
You can find links to graphs and comparison views for each of the above tests at: https://treeherder.mozilla.org/perf.html#/alerts?id=25667
On the page above you can see an alert for each affected platform as well as a link to a graph showing the history of scores for this test. There is also a link to a treeherder page showing the Talos jobs in a pushlog format.
To learn more about the regressing test(s), please see: https://wiki.mozilla.org/TestEngineering/Performance/Talos
For information on reproducing and debugging the regression, either on try or locally, see: https://wiki.mozilla.org/TestEngineering/Performance/Talos/Running
*** Please let us know your plans within 3 business days, or the offending patch(es) will be backed out! ***
Our wiki page outlines the common responses and expectations: https://wiki.mozilla.org/TestEngineering/Performance/Talos/RegressionBugsHandling
Reporter | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
Thank you for the information. The patches have already been backed out for other scrolling-related regressions. I will use this bug to track the performance-related part of the regression.
Updated•5 years ago
|
Updated•5 years ago
|
Comment 2•4 years ago
|
||
(In reply to Chris Martin [:cmartin] from comment #1)
Thank you for the information. The patches have already been backed out for other scrolling-related regressions. I will use this bug to track the performance-related part of the regression.
Hi Chris, should you be assigned to this bug and do you forecast an uplift to beta? Thanks
Assignee | ||
Comment 3•4 years ago
|
||
(In reply to Pascal Chevrel:pascalc from comment #2)
(In reply to Chris Martin [:cmartin] from comment #1)
Thank you for the information. The patches have already been backed out for other scrolling-related regressions. I will use this bug to track the performance-related part of the regression.
Hi Chris, should you be assigned to this bug and do you forecast an uplift to beta? Thanks
Good catch! I just took ownership of the bug.
I don't think it will need an uplift - This feature is a security enhancement that is not tied to a specific release.
Updated•4 years ago
|
Comment 5•4 years ago
|
||
The severity field is not set for this bug.
:gcp, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 6•4 years ago
|
||
We're not shipping this and it's been backed out for now, so the performance impact is moot.
Comment 7•4 years ago
|
||
The severity field is not set for this bug.
:gcp, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Comment 8•4 years ago
|
||
I'm just going to set this bug to 'wontfix', since the changeset that caused it has already been backed out and any similar changeset in the future will likely have different perf characteristics.
Updated•4 years ago
|
Description
•