I think it fits here. 😃 And there is also #news-and-articles

nice, thanks for sharing. Unfortunately it looks like it won’t be supported by oracle and we’d like to switch to Graal VM for the polyglot support so we can’t use it but it looks really impressive.

> the application as a whole, not only the GC phase, is slower with Shenandoah GC which specific resource gets restrained? (e.g. CPU)

@U45T93RA6 I believe that's due to the concurrent sweeps i.e. that you must pay the latency cost during GC passes, even though they're individually small. I work at a Go shop and there are a lot of similarities between Go's mark & sweep GC and Shenandoah. One makes the same trade-off with throughput.

This is because Shenandoah uses forwarding pointers and memory barriers for each object field access. It must do that so that compaction (relocation) can happen concurrently with the application.