Closed Bug 1666229 Opened 4 years ago Closed 4 years ago

1.21 - 7.8% tp5o responsiveness / tp5o_webext responsiveness (linux64-shippable, linux64-shippable-qr) regression on push 85cff42af3a321f95791fb66cde1aff70107693c (Wed September 16 2020)

Categories

(Core :: JavaScript Engine, defect)

Firefox 82
defect

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox-esr78 --- unaffected
firefox80 --- unaffected
firefox81 --- unaffected
firefox82 --- fix-optional
firefox83 --- affected

People

(Reporter: alexandrui, Unassigned)

References

(Regression)

Details

(4 keywords)

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

Regressions:

8% tp5o responsiveness linux64-shippable-qr opt e10s stylo 1.58 -> 1.70
4% tp5o_webext responsiveness linux64-shippable opt e10s stylo 2.16 -> 2.26
4% tp5o_webext responsiveness linux64-shippable-qr opt e10s stylo 2.51 -> 2.60
1% tp5o_webext responsiveness linux64-shippable-qr opt e10s stylo 2.58 -> 2.61

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.

Flags: needinfo?(jcoppeard)
Component: Performance → JavaScript Engine
Product: Testing → Core

It seems that this benchmark doesn't measure responsiveness (see bug 1665600) but it may indicate that the performance of full GC changed.

Setting up flags based on the time when the regressor Bug 844755 landed.

Given the comments in bug 1665600 I don't think we should pay much attention to this benchmark at the moment.

Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(jcoppeard)
Resolution: --- → WONTFIX
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.