Add tuning parameters for new malloc memory counter
Categories
(Core :: JavaScript: GC, task, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox70 | --- | fixed |
People
(Reporter: jonco, Assigned: jonco)
References
Details
Attachments
(2 files)
At the moment this uses the base parameter for the original malloc allocation counter and a fixed growth factor of 2. This bug will add individual parameters for these and set them to something the approximates the current behaviour.
Assignee | ||
Comment 1•5 years ago
|
||
We impose a minimum heap growth factor so that the new threshold must always be greater than the level at the end of a collection, otherwise we could get stuck endlessly collecting. The problem is that we can eagarly collect before we hit the threshold so this needs to be taken into account. At the moment we have two miminums though and we could simplifiy this to just a single one.
Depends on D39728
Assignee | ||
Comment 2•5 years ago
|
||
This adds two new parameters. The growth fator is set to 1.5 and the base to 42MB. Trail and error showed that this latter value ended up triggering GCs roughtly in line with the old malloc counter. These values make the initial malloc threshold ~64MB.
Depends on D39729
Updated•5 years ago
|
Updated•5 years ago
|
Comment 4•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/9b0221b3e7ea
https://hg.mozilla.org/mozilla-central/rev/c27a6d5810fe
Description
•