I’m not saying that the Go GC isn’t tuned for latency above all else (it is, to its detriment IMO). I’m saying that you can have an ultra-low-latency copying GC.
-
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
Replying to @sayrer
I don’t think so. Java HotSpot does escape analysis just as Go does. It is true that Go *relies* on escape analysis a lot more.
1 reply 0 retweets 0 likes -
This Tweet is unavailable.
-
It is Java...they could just be doing it cos 90s overengineering
1 reply 0 retweets 0 likes -
Replying to @tarasglek @sayrer
Probably. Java HotSpot is still the best GC around for *most* apps. People keep trying to improve on it and they usually end up making it worse. Remember, throughput matters just as much as latency for most apps!
1 reply 0 retweets 0 likes -
Except that server apps don't use it. Most stuff seems to be using g1gc
1 reply 0 retweets 0 likes -
Replying to @tarasglek @sayrer
I’m grouping all of the HotSpot collectors, G1 included, under “HotSpot” here.
1 reply 0 retweets 0 likes -
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
1 reply 0 retweets 0 likes
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 %).
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.