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.
-
-
Yes, malloc is slower than stack allocation. So obviously if performance matters you're going to avoid it. ButI would argue this mainly happens during normal program optimization / tuning, and not because Go's malloc (originally a tcmalloc fork) is particularly slow.
-
Go’s malloc is incredibly slow relative to bump allocation. Bump allocation is a single-digit number of instructions. e.g. https://github.com/dotnet/coreclr/blob/8e48db2c113052ef18cdafb43e114a8633864ec0/src/vm/i386/jitinterfacex86.cpp#L461 …
- 4 more replies
New conversation -
-
-
to satisfy your curiosity, you'd want an entirely new GC in the Go runtime? care to share the evidence you have?
-
Still waiting on that evidence
- 3 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.