5 ms·
On the go-nuts list people have been reporting large slowdowns with the new precise GC, and someone even backported the old GC to Go 1.1.
by fulafel 14y ago
On the go-nuts list people have been reporting large slowdowns with the new precise GC, and someone even backported the old GC to Go 1.1.
- Raphael_Amiard 14y ago> with the new precise GC The new GC is still not a precise GC, it's still conservative and non-tracing, just "more precise" (probably means they refined their heuristics) so you should probably not call it a precise GC.
- deleted 14y ago[deleted]
- asb 14y agoI thought Go 1.1 featured precise GC on the heap and conservative on the stack. Is that incorrect?
- coldtea 14y agoSo much for the GC that would improve on the old one... Google could spend some cash to get them a real GC expert to work with the Go team, like they did for JS.