Re:Go’s march to low-latency GC
by sievebrain on Thursday July 07, 2016 @05:17AM
(#12048296)
My understanding: C4 does not pause but the JVM still does for various other reasons and a part of the work on Zing has been forcing down those pause times too.
Sorta kinda all of the above.
C4 the algo has no pauses, but individual threads stop to crawl their own stacks. i.e., threads stop doing mutator work, but only 1-by-1, and only for a very short partial self-stack crawl.
C4 the impl I believe now has no pauses also.
HotSpot the JVM has pauses, and yes much Zing was on forcing these pause times down.
Cliff
To my knowledge this is false. AFAIK while the C4 algorithm is pauseless the C4 implementation is not. It's just that the pauses are really short.