3 ms·
Except that Java already has G1GC[0], a region-based collector. And if you're willing to shell out money there even is a pauseless, fully concurrent collector[1
by the8472 10y ago
Except that Java already has G1GC[0], a region-based collector. And if you're willing to shell out money there even is a pauseless, fully concurrent collector[1] scaling to hundreds of gigabytes.
[0] https://docs.oracle.com/javase/8/docs/technotes/guides/vm/gctuning/g1_gc.html https://docs.oracle.com/javase/8/docs/technotes/guides/vm/gc...
[1] https://www.azul.com/products/zing/pgc/ https://www.azul.com/products/zing/pgc/
- merb 10y agoWith Java 9 or 10 (doesn't remember) it gets a new Pausless GC, too. Not like the Azul one that works even with low Memory. But for high memory stuff.
- the8472 10y agoShenandoah[0]. From what I've read it's contributed to openjdk by redhat. Their claims about pause times aren't quite as strong as those of Azul, but <100ms pauses for 100GB+ heaps will still be leagues ahead of most GCs. It's probably also be less CPU-efficient than azul's, since it uses forwarding pointers instead of page table trickery. But if you have such a large heap you'll also have many cores. Here's a performance comparison to G1[1]. [0] http://openjdk.java.net/jeps/189 http://openjdk.java.net/jeps/189 [1] https://rkennke.wordpress.com/ https://rkennke.wordpress.com/