On: Proposed New Go GC: Transaction-Oriented Collector

[voidlogic]

The Go 1.7 GC is already on par with most Java GCs and arguably better. Our Go projects with large heaps now have better pause times than the similar Java programs, all having tried many of the Java GCs...

[icholy → voidlogic]

Not sure if it's better, it just has less work to do. Java creates a lot more garbage.

[stcredzero → icholy]

Whatever works. It's the result that counts.

[icholy → stcredzero]

ofc, I was strictly speaking about the GC algorithm.

[voidlogic → icholy]

Fair enough, I was comparing the application + runtime interaction, basically I, app behavior.

>Java creates a lot more garbage.

Very true, Go is great about keeping things on the stack.

Also sync.Pool helps a lot when used as needed.

[twic → voidlogic]

Part of the reason for this is that Java GC development has focused more on throughput, whereas Go GC development has focused more on pause time. It's rather hard to compare throughput between two such different languages, though.