Closed
Bug 1827621
Opened 2 years ago
Closed 2 years ago
Add a minium heap size threshold at which to use parallel marking
Categories
(Core :: JavaScript: GC, task, P3)
Core
JavaScript: GC
Tracking
()
RESOLVED
FIXED
114 Branch
| Tracking | Status | |
|---|---|---|
| firefox114 | --- | fixed |
People
(Reporter: jonco, Assigned: jonco)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Benchmark results show that parallel marking is not a win for small heap sizes on all systems.
| Assignee | ||
Comment 1•2 years ago
|
||
Benchmark results show that using parallel marking is not always a win for
small heaps, so add a threshold for its use.
This is set to 10MB, which will result in using parallel marking ~70% of the
time.
This parameter is set to zero for jit-tests and shell js tests so we get test
coverage where heap sizes are expected to be small (and maximum performance is
not a goal).
Pushed by jcoppeard@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/127346707e74
Add a mininum heap size threashold at which to use parallel marking r=sfink
Comment 3•2 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox114:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 114 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•