[meta] Fission MemShrink: reduce memory usage of content processes
Categories
(Core :: DOM: Content Processes, task, P2)
Tracking
()
People
(Reporter: cpeterson, Unassigned)
References
(Depends on 2 open bugs, Blocks 1 open bug)
Details
(Keywords: meta)
|
||
Updated•4 years ago
|
|
||
Comment 1•4 years ago
|
||
We already have bug 1436250 on file for this. I don't know if you want to start fresh or something.
|
Reporter | |
Comment 2•4 years ago
|
||
Randell says Fission's pre-alloced content processes on Linux are about 16.5 MB while Chrome’s zygote process is about 10 MB.
|
|
Reporter | |
Comment 3•4 years ago
|
||
(In reply to Andrew McCreight [:mccr8] from comment #1)
We already have bug 1436250 on file for this. I don't know if you want to start fresh or something.
I didn't realize there was already a meta bug for content process memory usage. Let's keep this fission-memshrink meta bug open for now while we do some initial investigation of Fission and Randell's new content process pre-allocation. Then we can decide whether to dupe this bug to bug 1436250.
|
||
Comment 4•4 years ago
|
||
Feel free to revive the Fission Memory wiki as well, it's got some useful information for this type of work. We've got the AWSY base memory test for tracking memory usage, right now the lower bound there looks ~18.25MB.
Also note we have a fork server (bug 1470591) landed that's intended to be used by fission. I'd take a look at that before kicking off a new project.
|
||
Comment 5•4 years ago
|
||
Closing this bug in favour of Bug 1436250.
Description
•