Closed Bug 1793417 Opened 4 years ago Closed 4 years ago

8.46 - 7.54% glterrain / glterrain (Windows) regression on Tue September 20 2022

Categories

(Core :: XPCOM, defect)

defect

Tracking

()

RESOLVED INVALID
Tracking Status
firefox-esr102 --- unaffected
firefox105 --- unaffected
firefox106 --- unaffected
firefox107 --- wontfix
firefox108 --- wontfix

People

(Reporter: afinder, Unassigned)

References

(Regression)

Details

(4 keywords)

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

Regressions:

Ratio Test Platform Options Absolute values (old vs new)
8% glterrain windows10-64-shippable-qr e10s fission stylo webrender 1.65 -> 1.79
8% glterrain windows10-64-shippable-qr e10s fission stylo webgl-ipc webrender 1.68 -> 1.81

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) may be backed out in accordance with our regression policy.

If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a sheriff to do that for you.

For more information on performance sheriffing please see our FAQ.

Flags: needinfo?(florian)

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

I'm not sure I'm reading the perfherder charts correctly, but I see a yellow line that says "pupper host configuration management" right before the change in the numbers. What does it mean? Could it be the cause, rather than the patch?

Flags: needinfo?(florian) → needinfo?(afinder)

:alex finder could you take a look at the question in comment 2?
(107 goes to beta on 2022-10-17)

Pref values seem to be back to the value before the patch landed.
Could someone confirm?

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

Closing as invalid - see Comment 4

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