3 ms·
Simpler would be "just work like I expect".
by dboreham 9y ago
Simpler would be "just work like I expect".
- zaarn 9y agoDoesn't work with GCs. As another comment in this thread explained, GCs have CPU and Memory tradeoffs and you can easily make a GC that would work excellent in the OP benchmark but would suffer severely under other workloads.
- merlish 9y agoI think the expectation the Go lot have been working towards is the expectation that individual pauses are very short. Contrast to a Java server GC, aiming towards overall efficiency. (Tell me if I'm wrong, I'm no expert.)
- falcolas 9y agoWhat about the use cases where what you expect is not what I expect? GC is, as a sibling comment says, about compromises around memory safety.
- weberc2 9y agoAs another commented posted elsewhere, GC is all about tradeoffs, and for a govern set of GC tradeoffs there will always be pathological cases. Another GC might work out of the box for this workload, but perform very badly for a workload at which Go's GC excels. As others have already mentioned, the fact that he was so easily able to tune the GC is a testament to Go's simplicity. There are lots of good criticisms of Go to be had, but it's runtime is pretty remarkable, in my opinion.