JavaScript:SpiderMonkey:GC Futures: Difference between revisions

Line 7: Line 7:
* Speed up allocator
* Speed up allocator
** remove or mitigate locking ????
** remove or mitigate locking ????
** need more here????
** [https://bugzilla.mozilla.org/show_bug.cgi?id=506174 ]
** [https://bugzilla.mozilla.org/show_bug.cgi?id=506174 Use one single GC heap chunk, avoiding frequent mmap and malloc calls]
* Speed up collector
* Speed up collector
** Allocate short-enough strings from GC heap, not malloc heap [bug NNNNNN]
** Allocate short-enough strings from GC heap, not malloc heap [bug NNNNNN]
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=402614 study string populations]
** Allocate object dslots from GC heap, not malloc heap? Alternative: [bug NNNNNN]
** Allocate object dslots from GC heap, not malloc heap? Alternative: [bug NNNNNN]
** Based on [https://bugzilla.mozilla.org/show_bug.cgi?id=502736 Gregor's stats] consider making 32-byte and 64-byte JSObjects to cover most cases except large objects without any dslots [bug NNNNNN]
** Based on [https://bugzilla.mozilla.org/show_bug.cgi?id=502736 Gregor's stats] consider making 32-byte and 64-byte JSObjects to cover most cases except large objects without any dslots [bug NNNNNN]
546

edits