Open Bug 1895678 Opened 7 months ago Updated 6 months ago

7.54 - 4.26% pdfpaint colorspace_atan.pdf / pdfpaint bug1650302_reduced.pdf + 6 more (Linux, OSX, Windows) regression on Thu April 25 2024

Categories

(Core :: JavaScript Engine, defect, P2)

defect

Tracking

()

ASSIGNED
Tracking Status
firefox-esr115 --- unaffected
firefox125 --- unaffected
firefox126 --- unaffected
firefox127 --- wontfix
firefox128 --- fix-optional

People

(Reporter: bacasandrei, Assigned: alexical)

References

(Blocks 1 open bug, Regression)

Details

(4 keywords, Whiteboard: [sp3])

Perfherder has detected a talos performance regression from push fa120d93961efddd63d50135f03c55e75dac875a. 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)
8% pdfpaint colorspace_atan.pdf macosx1015-64-shippable-qr e10s fission stylo webrender 406.01 -> 436.61
5% pdfpaint colorspace_atan.pdf linux1804-64-shippable-qr e10s fission stylo webrender-sw 482.31 -> 508.68
5% pdfpaint colorspace_sin.pdf macosx1015-64-shippable-qr e10s fission stylo webrender-sw 403.70 -> 424.58
5% pdfpaint colorspace_cos.pdf windows10-64-shippable-qr e10s fission stylo webrender-sw 387.21 -> 406.71
5% pdfpaint colorspace_cos.pdf macosx1015-64-shippable-qr e10s fission stylo webrender 402.10 -> 421.98
5% pdfpaint colorspace_atan.pdf linux1804-64-shippable-qr e10s fission stylo webrender-sw 486.88 -> 510.62
4% pdfpaint colorspace_sin.pdf windows10-64-shippable-qr e10s fission stylo webrender-sw 389.20 -> 406.24
4% pdfpaint bug1650302_reduced.pdf windows10-64-shippable-qr e10s fission stylo webrender-sw 308.33 -> 321.47

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.

You can run these tests on try with ./mach try perf --alert 77

For more information on performance sheriffing please see our FAQ.

Flags: needinfo?(dothayer)

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

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

Assignee: nobody → dothayer
Status: NEW → ASSIGNED
Flags: needinfo?(dothayer)
Blocks: 1803803
Severity: -- → S3
Priority: -- → P2

Still poking at this, but I feel like it's some kind of pathology in the benchmarking setup, because I can't reproduce this when I just try to render the file locally. If anything I see a slight improvement, but certainly not a 5% regression.

Whiteboard: [sp3]
You need to log in before you can comment on or make changes to this bug.