Allocate GC chunks from jemalloc
Categories
(Core :: JavaScript: GC, enhancement, P5)
Tracking
()
People
(Reporter: pbone, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: memory-footprint, Whiteboard: [MemShrink:P2])
I was speaking with glandium and he suggested allocating our 1MB chunks from jemalloc so that the single resource of memory is managed in one place. We may avoid running out of address space on 32bit this way.
Reporter | ||
Updated•5 years ago
|
Comment 1•5 years ago
|
||
(In reply to Paul Bone [:pbone] from comment #0)
jemalloc is not currently required to build SpiderMonkey. But if it was, how would this help to avoid running out of address space? It makes sense to manage resources in one place, but I don't know what you're specifically proposing here.
Reporter | ||
Comment 2•5 years ago
|
||
It came from a discussion with gladium, he made the assertion but I don't know exactly what he was thinking, my thought is that it means there's only be a single place managing a pool of spare memory. For example if we have some spare chunks but jemalloc does not and jemalloc wants some to satisfy an allocation, it cannot ask us for one of our chunks and must instead mmap some new memory.
Comment 3•5 years ago
|
||
(In reply to Paul Bone [:pbone] from comment #2)
OK, so the idea is to have jemalloc manage the free chunks list. Thanks.
Updated•5 years ago
|
Reporter | ||
Comment 4•5 years ago
|
||
(In reply to Jon Coppeard (:jonco) from comment #3)
(In reply to Paul Bone [:pbone] from comment #2)
OK, so the idea is to have jemalloc manage the free chunks list. Thanks.
Yes.
Updated•5 years ago
|
Updated•2 years ago
|
Description
•