3 ms·
I didn't know about .NET permitting interior pointers. Thanks. I think you're right about HotSpot GC not using read barriers. I was mixing it up with the Azul
by ngrilly 9y ago
I didn't know about .NET permitting interior pointers. Thanks.
I think you're right about HotSpot GC not using read barriers. I was mixing it up with the Azul GC, which uses read barriers.
> If you have concurrent mark-and-sweep and stop the world only during compaction phases, read barriers are unnecessary.
Do you know if it's possible to bound the pause caused by the compaction phase to some ceiling, like 2 ms for example? I'm asking because it's a goal of Go' GC to limit GC pauses.