Closed Bug 1799488 Opened 3 years ago Closed 3 years ago

18.66% microsoft loadtime (OSX) regression on Sat October 22 2022

Categories

(Core :: DOM: Forms, defect)

defect

Tracking

()

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

People

(Reporter: afinder, Unassigned)

References

(Regression)

Details

(Keywords: perf, perf-alert, regression)

Attachments

(1 file)

Perfherder has detected a browsertime performance regression from push 8baa19d12931bdf9b5d61ea4f06a9d6b8e214d81. 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)
19% microsoft loadtime macosx1015-64-shippable-qr cold fission webrender 256.96 -> 304.92

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?(avandolder)

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

Attached image image.png —

Hard to say that this landing caused this. It's a very noisy test that seems to have gotten noisier around the landing, but I wouldn't say blame is definitive. Also the 19% regression is questionable.

I'm really unsure of how this regression could've been caused by this patch; the change should be pretty much trivial.

Flags: needinfo?(avandolder)

Hi Alex,

Adam's patch isn't in the regression range you posted in the description, so we are a bit confused here. Also, as Jim noted, the graph was noisy and looks like something was improved around Oct 29.

Can you clarify those for us? Thanks!

Flags: needinfo?(afinder)

There is a visible difference between revisions 8baa19d12931b and a374e40ad4e2f, making bug 1795887 as the actual culprit. Regression seems to have been resolved around d1982cee06ca5. Backfilled range d1982cee06ca5 - caddc49839d30 to see if there is still a regression visible after that, or it's just noise.

Flags: needinfo?(afinder)
Flags: needinfo?(afinder)

Closing bug and alert as invalid due to noise. Sorry for the confusion!

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

Attachment

General

Created:
Updated:
Size: