Closed Bug 1625420 Opened 5 years ago Closed 2 years ago

6.9% raptor-tp6-fandom-firefox-cold fcp (linux64-shippable-qr) regression on push 93cf130f59f97acc6ebb84c3505880cdcaca36c0 (Tue March 24 2020)

Categories

(Core :: Graphics: WebRender, defect, P3)

76 Branch
defect

Tracking

()

RESOLVED WONTFIX
mozilla76
Tracking Status
firefox-esr68 --- unaffected
firefox74 --- unaffected
firefox75 --- unaffected
firefox76 --- wontfix

People

(Reporter: marauder, Unassigned)

References

(Regression)

Details

(Keywords: perf, perf-alert, regression)

Raptor has detected a Firefox performance regression from push:

https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=93cf130f59f97acc6ebb84c3505880cdcaca36c0

As author of one of the patches included in that push, we need your help to address this regression.

Regressions:

8% raptor-tp6-fandom-firefox-cold fcp linux64-shippable-qr opt 707.50 -> 764.75
7% raptor-tp6-fandom-firefox-cold fcp linux64-shippable-qr opt 712.71 -> 761.92

You can find links to graphs and comparison views for each of the above tests at: https://treeherder.mozilla.org/perf.html#/alerts?id=25502

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 Raptor jobs in a pushlog format.

To learn more about the regressing test(s) or reproducing them, please see: https://wiki.mozilla.org/TestEngineering/Performance/Raptor

*** 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

Blocks: 1622755
Component: Performance → Graphics: WebRender
Flags: needinfo?(aosmond)
Product: Testing → Core
Regressed by: 1622254
Target Milestone: --- → mozilla76
Version: Version 3 → 76 Branch
Has Regression Range: --- → yes

That's certainly interesting. I know the comparison is a little more expensive, but hard to believe it would cause an issue. The tiling need may have caused some machinery underneath to change. There are no other nearby changes which seem relevant so I'm confident it is indeed my change that triggered it (but unlikely to be directly responsible for the regression).

Flags: needinfo?(aosmond)
Priority: -- → P3

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)

Severity: normal → S3

Too old to fix now.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.