5 ms·

What’s wrong with Go‘s GC. I think it’s actually pretty fast and gets better with each release.

• pjmlp 6y ago
  Plenty of stuff, https://github.com/golang/go/issues/42430 https://github.com/golang/go/issues/42430 As usual, Go knows better than other the older languages and then a kludge solution gets done.
  • agnivade 6y ago
    It seems to me like your opinion about Go GC is that it is an extremely buggy and slow piece of software. Every software has bugs. Whether those bugs are a major blocker for people to use them or not should be taken into account. The issue that you pointed out are difficult items which need more time and thought to take care of. But they aren't something which should cause any major pain in your day-to-day usage of Go. I would say as of 1.15, GC has improved by leaps and bounds and at this point, all major warts with the system are taken care of. But then again, I don't know in what context you are using Go. It may be the case that you have been affected by any of these bugs, and unless they get fixed, using Go is a blocker for you.
• WJW 6y ago
  It's not particularly fast, for instance. The golang GC has pretty short pause times but its actual throughput in GB/s collected does not stand out. Short pause times are nice for interactive systems but don't matter as much for eg batch or background jobs, where total time to completion is much more important. The sister comment also has a link to a GH issue detailing many more specific flaws of the GC.