Closed
Bug 1790336
Opened 2 years ago
Closed 2 years ago
Tune balanced heap limits to give parity on benchmarks
Categories
(Core :: JavaScript: GC, task, P2)
Core
JavaScript: GC
Tracking
()
RESOLVED
FIXED
106 Branch
Tracking | Status | |
---|---|---|
firefox106 | --- | fixed |
People
(Reporter: jonco, Assigned: jonco)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
It's important that using balanced heap limits doesn't regress performance for users.
Assignee | ||
Comment 1•2 years ago
|
||
This limits the heap growth when using balanced heap limits to a factor of 3.
This allows increasing the heap growth factor so the heap can grow rapidly when
where is a lot of allocation happening without affecting memory use too badly.
Assignee | ||
Comment 2•2 years ago
|
||
Increasing this parameter gives us parity on our benchmarks in the testing I've
done so far.
Depends on D157094
Updated•2 years ago
|
Severity: -- → S3
Priority: -- → P2
Pushed by jcoppeard@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/93bf49a3911b Part 1: Limit heap growth to sensible limit r=sfink https://hg.mozilla.org/integration/autoland/rev/a0110fc4a82e Part 2: Increase balanced heap growth factor r=sfink
Comment 4•2 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/93bf49a3911b
https://hg.mozilla.org/mozilla-central/rev/a0110fc4a82e
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox106:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 106 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•