I hear that -XX:MaxGCPauseMillis=20 works better when you use it with -XX:+GuaranteeToothFairyExists
-
Go claims they’ve made this work. Interrupting threads?
.@jamie_allen Go's (current) collectors don't compact. Different problem space. Not compacting in Java mean not running very long.
-
-
and even Go doesn't call their hopeful targets *max* GC pause times.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
why can't we just remove Xmx, maybe remove compaction and use heuristics to know when to GC ?
-
Zing actually does elastic memory for the heap. Xmx sets the committed memory, but we can go over…
End of conversation
New conversation -
-
-
why can Go get away with it, because it’s not generational?
-
I don't know that they actually get away with it. Current long running apps in go are the ones getting away with it. Circular.
-
interesting. Thx.
-
Tweet unavailable
-
I hadn’t delved into these claims and was wondering if/how they’d pulled this off
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.