4 ms·
The Go team were very proud of their garbage collector that “virtually eliminates” (IIRC) GC pauses. I guess it does that at the cost of severe program slowdown
by TazeTSchnitzel 9y ago
The Go team were very proud of their garbage collector that “virtually eliminates” (IIRC) GC pauses. I guess it does that at the cost of severe program slowdown in cases like this? It's all about trade-offs, and I don't trust people who think there's only one thing to optimise for.
- kibwen 9y agoWhile the Go GC is definitely no slouch when it comes to engineering, the messaging around it has not been entirely forthright: https://blog.plan99.net/modern-garbage-collection-911ef4f8bd8e https://blog.plan99.net/modern-garbage-collection-911ef4f8bd...
- geodel 9y agoThis blog is more of a rant. Official blog announcements and marketing material are not the place to delve deeply into technical tradeoffs of designing GC. He compares it with Java which is rather ironic considering I have not seen Java official announcements talking about things not done. It would like saying 'We have not been able to deliver value types, module story is still half done, and we couldn't write an official http cient in whole development cycle in Java 9' in release announcement of Java 9. Also there is no data provided to show how bad is Go's GC compare to Java