1869039 - 52.71 - 39.4% twitch ContentfulSpeedIndex / twitch loadtime (Linux, OSX) regression on Fri December 1 2023

Status: RESOLVED WONTFIX

(Testing :: Raptor, defect)

Description

[Alex Finder]

Perfherder has detected a browsertime performance regression from push 68378d2409bc693ef00f3f157ecaea7067df7edc. 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)
53%	twitch ContentfulSpeedIndex	linux1804-64-shippable-qr	fission warm webrender	304.95 -> 465.67
39%	twitch loadtime	macosx1015-64-shippable-qr	fission warm webrender	541.35 -> 754.62

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

Comment 1

[BugBot [:suhaib / :marco]]

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

Comment 2

[Greg Mierzwinski [:sparky]]

:afinder, can you double-check this regression? The pushlog changeset seems to be pointing to a different commit.

Comment 3

[Alex Finder]

Hi Sparky! Sorry for the confusion here, I wanted to open a bug for pushlog faeaf5bd4445bd6831e09956e6f78eb06629517d, but the generated alert for that doesn't allow filing a bug, since there are too many alerts linked to that alert summary and the generated request is too large. The regression is still for bug 1863130.

Comment 4

[Greg Mierzwinski [:sparky]]

Ok, thanks! We can close this as wontfix since it was caused by a re-recording of twitch, and imgur.

Comment 5

[Alex Finder]

Thanks sparky! Sounds good to me, closed the alert as WONTFIX as well.