JavaScript:SpiderMonkey:GC Futures: Difference between revisions

Line 13: Line 13:
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=402614 study string populations]
*** [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 [https://bugzilla.mozilla.org/show_bug.cgi?id=508357 bug 508357]
* Remove byte flag per thing design [bug NNNNNN]
* Remove byte flag per thing design [bug NNNNNN]
** Bad cache effects of flags and things allocated from opposite ends of same arena
** Bad cache effects of flags and things allocated from opposite ends of same arena
546

edits