Open Bug 1791547 Opened 15 days ago Updated 21 hours ago

Enable balanced heap limits

Categories

(Core :: JavaScript: GC, task, P1)

task

Tracking

()

REOPENED

People

(Reporter: jonco, Assigned: jonco, NeedInfo)

References

(Blocks 1 open bug)

Details

(Keywords: perf-alert)

Attachments

(1 file)

The last performance tests I did showed no regressions and it's the start of the cycle, so let's try enabling balanced heap limits everywhere. If this causes problems we can back it out straight away.

Note to sheriffs: this may cause performance changes.

This is not enable for fuzzing builds or in the shell if the fuzzing safe
option is passed.

Assignee: nobody → jcoppeard
Status: NEW → ASSIGNED
Severity: -- → N/A
Priority: -- → P1
Pushed by jcoppeard@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/4c043a955561
Enable balanced heap limits by default r=sfink
Status: ASSIGNED → RESOLVED
Closed: 14 days ago
Resolution: --- → FIXED
Target Milestone: --- → 107 Branch
Regressions: 1792394
Status: RESOLVED → REOPENED
Flags: needinfo?(jcoppeard)
Resolution: FIXED → ---
Target Milestone: 107 Branch → ---

(In reply to Pulsebot from comment #2)

Pushed by jcoppeard@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/4c043a955561
Enable balanced heap limits by default r=sfink

== Change summary for alert #35516 (as of Mon, 26 Sep 2022 05:24:53 GMT) ==

Regressions:

Ratio Test Platform Options Absolute values (old vs new)
4% imdb loadtime android-hw-a51-11-0-aarch64-shippable-qr warm webrender 3,107.54 -> 3,241.12

For up to date results, see: https://treeherder.mozilla.org/perfherder/alerts?id=35516

You need to log in before you can comment on or make changes to this bug.