logoalt Hacker News

virtualSatai • today at 7:40 AM • 1 reply • view on HN

If you read the link you'll see that they found out go forces a GC every two minutes no matter the amount of garbage.


Replies

masklinn • today at 8:27 AM

And importantly in a tracing GC the work load is a function of the non-garbage data not of the garbage.

Generational GC can avoid some of it by ignoring the old code entirely, but Go does not implement generations because its relatively strong ability to stack-allocate generally replaces the nursery, and for most work loads you don’t recoup the costs.