Closed Bug 1974484 Opened 1 year ago Closed 11 months ago

Multiple regressions on JS3, six-speed, and web-tooling benchmark around 26june 2025

Categories

(Core :: JavaScript Engine, defect)

defect

Tracking

()

RESOLVED FIXED
Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- unaffected
firefox-esr140 --- unaffected
firefox140 --- unaffected
firefox141 --- unaffected
firefox142 --- fixed

People

(Reporter: mayankleoboy1, Unassigned)

References

(Regression)

Details

(Keywords: regression)

Summary: 54% regression on six-speed-template-string-es5 around 26june 2025 → Multiple regressions on six-speed and web-tooling benchmark around 26june 2025
Flags: needinfo?(iireland)

JS3 regressions:
8% on lebab-wtb

Summary: Multiple regressions on six-speed and web-tooling benchmark around 26june 2025 → Multiple regressions on JS3, six-speed, and web-tooling benchmark around 26june 2025

I downloaded the CI shell builds before and after bug 1960433 and tested six-speed-string-template-es5. I couldn't reproduce a regression: in both cases, the test gets optimized away to a boring empty loop.

I've taken a quick look at the other two and I don't see anything obvious.

Flags: needinfo?(iireland)

See also : https://bugzilla.mozilla.org/show_bug.cgi?id=1930281#c21 , where pieces of OMT baseline compilation landed, causes regression on benchamrks, but the analysis did not reveal anything much.

See Also: → 1930281

:sdetar since iain is on pto is there someone else that can take a look at this regressing bug?

Flags: needinfo?(sdetar)

Jan, could you take an initial look at this bug while Iain is out.

Flags: needinfo?(sdetar) → needinfo?(jdemooij)

We have some reported regressions here and a Speedometer 2 regression in bug 1975489. I did some bisecting on Try for the patch stack in bug 1960433:

  • Sp2 regression on AngularJS-TodoMVC/DeletingAllItems/Sync regressed by "Bug 1960433: Pass the ICScript in the stub frame instead of the JSContext r=jandem"
  • six-speed-template_string-es5: this test appears to be somewhat bimodal but we now get the slower result a lot more frequently than before starting with the same change as ^
  • web-tooling-benchmark-prettier: similar I think

It's a bit baffling because that change is fairly straight-forward. I'm testing a few small things on Try to see if I can blame it on a specific part of that patch, but it might just be noise from changing stack frame layout...

See Also: → 1975489

I tracked it down to an actual perf issue (bug 1960433 comment 20). This is fixed by backout now.

Status: NEW → RESOLVED
Closed: 11 months ago
Flags: needinfo?(jdemooij)
Resolution: --- → FIXED
QA Whiteboard: [qa-triage-done-c143/b142]
You need to log in before you can comment on or make changes to this bug.