546
edits
JavaScript:SpiderMonkey:GC Futures: Difference between revisions
JavaScript:SpiderMonkey:GC Futures (view source)
Revision as of 21:10, 4 August 2009
, 4 August 2009→JS GC Futures
| Line 7: | Line 7: | ||
* Speed up allocator | * Speed up allocator | ||
** remove or mitigate locking ???? | ** remove or mitigate locking ???? | ||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=506174 Use one single GC heap chunk, avoiding frequent mmap and malloc calls] | ** [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 402614] | ** Allocate short-enough strings from GC heap, not malloc heap [https://bugzilla.mozilla.org/show_bug.cgi?id=402614 bug 402614] | ||
** 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 [https://bugzilla.mozilla.org/show_bug.cgi?id=508357 bug 508357] | ** 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 [https://bugzilla.mozilla.org/show_bug.cgi?id=508357 bug 508357] | ||