Closed Bug 1681721 Opened 5 years ago Closed 5 years ago

3.78% glterrain (windows10-64-qr) regression on push 71d7e6400bae13f9b5501c3a1a12d83810254347 (Mon November 30 2020)

Categories

(Testing :: Performance, defect)

Product:
Testing
Component:
Performance
Version:
Firefox 85
Type:
defect

Tracking

(firefox85 affected)

Status:
RESOLVED INVALID
Tracking Flags:
Tracking Status
firefox85 --- affected

People

(Reporter: alexandrui, Unassigned)

Details

(4 keywords, Whiteboard: [perf:alert:0])

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

Regressions:

Ratio Suite Test Platform Options Absolute values (old vs new)
4% glterrain windows10-64-qr e10s stylo webgl-ipc webrender 2.00 -> 2.08

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?(pbone)
Component: Performance → Fuzzing
Product: Testing → Core

And browsertime improvment:

== Change summary for alert #28021 (as of Wed, 09 Dec 2020 05:35:35 GMT) ==

Improvements:

Ratio Suite Test Platform Options Absolute values (old vs new)
3% amazon-search FirstVisualChange android-hw-p2-8-0-android-aarch64-shippable nocondprof warm webrender 484.22 -> 469.75

For up to date results, see: https://treeherder.mozilla.org/perfherder/alerts?id=28021

This is unrelated, as the changes in bug 1677857 are behind the FUZZING ifdef and not active in the builds mentioned.

Flags: needinfo?(pbone)
Component: Fuzzing → Performance
Product: Core → Testing
No longer regressed by: 1677857

The prior push is bug 1679652, which at least looks related to Windows graphics. Maybe that is what caused it?

(In reply to Andrew McCreight [:mccr8] from comment #3)

The prior push is bug 1679652, which at least looks related to Windows graphics. Maybe that is what caused it?

Did some retriggers, need to revisit to confirm this.

Flags: needinfo?(aionescu)
Flags: needinfo?(aionescu)
Whiteboard: [perf:alert:0]

Reassigned to the alert linked to bug 1679652.

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