4 ms·
You will be doing battle with the GC in many of these applications. Yes, even 1.5+. 10ms is an eternity to do no workload.
by kev009 11y ago
You will be doing battle with the GC in many of these applications. Yes, even 1.5+. 10ms is an eternity to do no workload.
- tptacek 11y agoThe only service in this list that I can see the GC mattering for is NTP, but then, you can design a tight NTP server that virtually eliminates the GC's work in Go, taking advantage of the rest of Go's high-level features that C lacks.
- infogulch 11y agoFrom 1.5 to 1.6 @brianhatfield saw pauses in a 8GB heap & 150M allocs/min go from 40ms to ~3ms [0]. [0]: https://twitter.com/brianhatfield/status/692778741567721473 https://twitter.com/brianhatfield/status/692778741567721473