3 ms·

> It has been known since 1984 that most allocations “die young” i.e. become garbage very soon after being allocated. 1983: A Real-Time Garbage Collector Base

by lispm 10y ago

> It has been known since 1984 that most allocations “die young” i.e. become garbage very soon after being allocated. 1983: A Real-Time Garbage Collector Based on the Lifetimes of Objects, Lieberman/Hewitt http://web.media.mit.edu/~lieber/Lieberary/GC/Realtime/Realtime.html http://web.media.mit.edu/~lieber/Lieberary/GC/Realtime/Realt... Since objects with short lifetimes account for a large portion of storage use, it is worth optimizing a garbage collector to reclaim storage for these objects more quickly.

voidlogic 10y ago
I'd be interesting to know to what degree Go's aggressive stack-based allocation/escaping makes this hypothesis less strong than other languages. For example, Java a few generations ago was very poor at escaping heap allocation to the stack and so much the opposite skewing towards heap allocation over stack allocation, so I'm sure the JVMs of this era were an extremely good fit for the generational hypothesis.