Beware of drawing conclusions about generational GC from the Golang ISMM keynote. As far as I can tell, they didn’t test against copying generational GC with bump allocation in the nursery, which is the typical implementation.
In favor of generational: SpiderMonkey switched from a malloc scheme to generational GC, to significant performance improvements. Most of the wins came from—you guessed it—bump allocation in the nursery.
-
-
did you happen to write about it anywhere?
-
Yep, here’s a writeup with a simple benchmark. https://hacks.mozilla.org/2014/09/generational-garbage-collection-in-firefox/ … There’s lots of interesting stuff if you search for “spidermonkey generational gc” :)
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.