Re:Go 1.5 concurrent garbage collector pacing
by mike_hearn on Tuesday March 10, 2015 @05:44PM
(#9180870)
G1 is the most advanced and is where the main development seems to be happening (ignoring Shenandaoh which is a Red Hat project to create an Azul style virtually-pauseless megascale GC).
For example the G1 garbage collector can deduplicate strings in the heap. This can be a big win for servers and IDEs.
In the latest update I read that G1 is also able to adapt itself to memory pressure in the entire operating system. If you start an app next to the JVM and the OS available memory drops, it'll start to use more CPU time for collection and shrink the heap so it can hand RAM back to the OS and reduce pressure again.
G1 can do lots of other nifty things, but it uses more RAM than ParCMS so it's not the default at the moment. You have to opt into it. I think they want to make it the default one day.
For example the G1 garbage collector can deduplicate strings in the heap. This can be a big win for servers and IDEs.
In the latest update I read that G1 is also able to adapt itself to memory pressure in the entire operating system. If you start an app next to the JVM and the OS available memory drops, it'll start to use more CPU time for collection and shrink the heap so it can hand RAM back to the OS and reduce pressure again.
G1 can do lots of other nifty things, but it uses more RAM than ParCMS so it's not the default at the moment. You have to opt into it. I think they want to make it the default one day.