Open
Bug 1859006
Opened 2 years ago
Updated 1 year ago
[meta] Audit core GC types for wasted memory
Categories
(Core :: JavaScript: GC, task, P3)
Core
JavaScript: GC
Tracking
()
NEW
People
(Reporter: jonco, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: meta)
Attachments
(1 file)
|
19.15 KB,
text/plain
|
Details |
Using ptype/o in gdb is an easy way to show the memory layout of objects. Doing this on GCRuntime shows there are many places where the compiler is inserting padding and that some data members are larger than I expected (SortedArenaList is nearly 4KB).
It would be pretty straightforward to use this to tighten up the layout and perhaps see if we could do something about the larger data structures.
|
Reporter | |
Comment 1•2 years ago
|
||
|
||
Updated•2 years ago
|
Severity: -- → S3
Priority: -- → P3
|
||
Updated•2 years ago
|
Summary: Audit core GC types for wasted memory → [meta] Audit core GC types for wasted memory
|
||
Updated•1 year ago
|
Blocks: sm-runtime
Severity: S3 → N/A
You need to log in
before you can comment on or make changes to this bug.
Description
•