The non-copying nature of Go’s GC doesn’t have anything to do with its latency.
I’m grouping all of the HotSpot collectors, G1 included, under “HotSpot” here.
-
-
The very fact that every Java user tweaks heap sizes and gc algo also suggests that the model is broken. I don't see people defaulting to molesting the ocaml or go gc heuristics
-
Give it time :) Go GC has knobs too (max heap size and max heap % usage IIRC). The Java ones are better (max pause time is easier to understand than max heap %).
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.