Closed
Bug 1340822
Opened 7 years ago
Closed 7 years ago
Move nursery and caches from ZoneGroup back to the runtime
Categories
(Core :: JavaScript: GC, defect)
Core
JavaScript: GC
Tracking
()
RESOLVED
FIXED
mozilla54
Tracking | Status | |
---|---|---|
firefox54 | --- | fixed |
People
(Reporter: bhackett1024, Assigned: bhackett1024)
References
Details
Attachments
(1 file)
68.55 KB,
patch
|
jonco
:
review+
|
Details | Diff | Splinter Review |
The vision for bug 1323066 is to have separate nurseries for each zone group, to allow for single threaded access in a preemptively scheduled runtime. Right now, though, nurseries each require a minimum of 1MB of space for their allocated chunk, and having multiple enabled nurseries in a runtime will increase our memory usage. Pretty soon Quantum DOM work will be start using different zone groups for each tab group, and to avoid these memory regressions it would be good to move the nursery back to the runtime until we have a strategy for reducing the minimum memory required for a nursery and putting a limit on the per-runtime maximum amount of nursery memory. This is fine to do for a cooperatively multithreaded runtime. There is a similar issue for the caches now stored on the zone group, and previously stored on the runtime/context. Moving these back to the runtime will make ZoneGroup pretty lightweight and easily usable by Gecko for grouping zones. Sorry about the churn...
Attachment #8838887 -
Flags: review?(jcoppeard)
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → bhackett1024
Updated•7 years ago
|
Attachment #8838887 -
Flags: review?(jcoppeard) → review+
Pushed by bhackett@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/a40af83f562a Move nursery and caches from ZoneGroup back to the runtime, r=jonco.
Comment 2•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/a40af83f562a
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla54
You need to log in
before you can comment on or make changes to this bug.
Description
•