4 engineers on Hacker News describe using G1 GC first-hand: 3 endorse it, 0 regret it, 0 are mixed.
“I've had good luck cranking g1gc very high in prod and avoiding long collection times all together.”
endorse · production · acpdev · 2026-07-19 · source ↗ · wrong label?“moving to G1 brought this down to rarely exceeding 100ms, Shenandoah brought this down further to typically <10ms.”
endorse · production · Kognito · 2019-12-15 · source ↗ · wrong label?“With heaps of more than 20gb in size and a lot of churn CMS just doesn't cut it.”
endorse · production · 3 yr · notimetorelax · 2017-11-14 · source ↗ · wrong label?“It's true that G1 will, under duress, give up some heap to the OS, but it's not what you see in practice, without exceptional attention paid to tuning.”
neutral · production · barrkel · 2019-12-26 · source ↗ · wrong label?