Closed Bug 1930558 Opened 27 days ago Closed 6 days ago

Regression on sessionrestore and sessionrestore_no_auto_restore (windows only) around 16Oct2024

Categories

(Testing :: Performance, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1933912

People

(Reporter: mayankleoboy1, Unassigned)

References

Details

(Whiteboard: [fxp])

Summary: Regression on sessionrestore and sessionrestore_no_auto_restore around 16Oct2024 → Regression on sessionrestore and sessionrestore_no_auto_restore (windows only) around 16Oct2024

This is the zommed-in range. The point could be this, whih points to bug 1908423. The description of the bug sounds like they are adding additional data to sessionrestore, which would possible make the sessionrestore slower.

Whiteboard: [fxp]

The severity field is not set for this bug.
:fbilt, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(fbilt)
Severity: -- → S3
Flags: needinfo?(fbilt)
Priority: -- → P2

I created the following performance alert manually, 42846, based on multiple retriggers around the area of the culprit (the Perfcompare link displayed on the alert summary also suggests a clear regression for that revision). The sessionrestore_no_auto_restore graph mentioned in first comment doesn't seem to me like it generated a regression, it just looks noisy.

Depends on: 1933912

Thanks for the investigation, Alex! With your retriggers, the regressor became very clear to identify.

Thanks for noticing this Mayank, we suspect that recent database issues prevented an alert from being raised. Now that we have bug 1933912 I believe we can close this.

Status: NEW → RESOLVED
Closed: 6 days ago
Duplicate of bug: 1933912
Resolution: --- → DUPLICATE
No longer depends on: 1933912
You need to log in before you can comment on or make changes to this bug.