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.
-
-
"This is what everyone else is doing, therefore it's the right way?"
-
Nobody has done benchmarks here, and in the absence of those I’m going to go with what’s been known for decades. Especially since there’s evidence that Go’s memory allocation is too slow for many people, since they manually rearrange code to satisfy escape analysis.
- 6 more replies
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.