Closed Bug 1981540 Opened 11 months ago Closed 11 months ago

0.32% Base Content Explicit (Windows) regression on Fri August 1 2025

Categories

(Core :: CSS Parsing and Computation, defect, P3)

defect

Tracking

()

RESOLVED FIXED
143 Branch
Tracking Status
firefox-esr128 --- unaffected
firefox-esr140 --- unaffected
firefox141 --- unaffected
firefox142 --- unaffected
firefox143 --- fixed

People

(Reporter: intermittent-bug-filer, Assigned: keithamus)

References

(Regression)

Details

(Keywords: perf, perf-alert, regression)

Attachments

(1 file)

Perfherder has detected a awsy performance regression from push f5b95b5c2423739ee543a846a43fe47549a54a05. As author of one of the patches included in that push, we need your help to address this regression.

Please acknowledge, and begin investigating this alert within 3 business days, or the patch(es) may be backed out in accordance with our regression policy. Our guide to handling regression bugs has information about how you can proceed with this investigation.

If you have any questions or need any help with the investigation, please reach out to fbilt@mozilla.com. Alternatively, you can find help on Slack by joining #perf-help, and on Matrix you can find help by joining #perftest.

Regressions:

Ratio Test Platform Options Absolute values (old vs new)
0.32% Base Content Explicit windows11-64-24h2-shippable fission 8,205,269.67 -> 8,231,492.36

Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests.

If you need the profiling jobs you can trigger them yourself from treeherder job view or ask fbilt@mozilla.com to do that for you.

You can run all of these tests on try with ./mach try perf --alert 46138

The following documentation link provides more information about this command.

Flags: needinfo?(mozilla)

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

Duplicate of this bug: 1981538

Investigating how we can reduce this.

Flags: needinfo?(mozilla)

This shrinks PseudoMap down from a 91usize (for each Box) to 91u8.
This slight memory saving in each PseudoMap should add up to some
reasonable savings overall, without significantly impacting performance
(see
https://perf.compare/compare-lando-results?baseLando=146687&newLando=147253&baseRepo=try&newRepo=try&framewor=&framework=13)

Assignee: nobody → mozilla
Status: NEW → ASSIGNED
Severity: -- → S3
Priority: -- → P3
Pushed by mozilla@keithcirkel.co.uk: https://github.com/mozilla-firefox/firefox/commit/4d0c110c3366 https://hg.mozilla.org/integration/autoland/rev/c7f54313b6b4 Use Vec<T>+[Option<u8>; 91] over [Option<Box<T>>; 91] for PseudoMap r=emilio,firefox-style-system-reviewers
Status: ASSIGNED → RESOLVED
Closed: 11 months ago
Resolution: --- → FIXED
Target Milestone: --- → 143 Branch

somewhat less than 52KB improvement on Base content Explicit. \o/

But also a corresponding 11KB regression on Heap-unclassified.
So maybe consider adding memory reporter for this?

QA Whiteboard: [qa-triage-done-c144/b143]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: