|
|
|
|
|
|
by 010a
3641 days ago
|
|
|
Golang's more recent async GC changes begin to resemble Erlang's per-process GC in how they would affect overall system performance. When people talk about Go's GC freezes, they're talking about the spinup/spindown time before the async GC kicks in. That part is incomparable to Erlang, but its a part which has gotten much faster recently, specifically through virtue of becoming smaller. |
|
|
They resemble generational GC more than anything. Generational GC has some of the advantages of Erlang (though I think the traditional HotSpot generational GC will end up working better than the one Go is going with) in the minor collections, but not in the major collections.