8 ms·
This describes the state of GC like it was 10 years ago (and in a few places incorrectly), at least in Hotspot. Shameless promotion: try out the new G1 (-XX:+Us
by deadc0de 15y ago
This describes the state of GC like it was 10 years ago (and in a few places incorrectly), at least in Hotspot. Shameless promotion: try out the new G1 (-XX:+UseG1GC), better to use the latest EA JDK7 build.
- jwr 15y agoG1 isn't necessarily the right solution for everyone. In my measurements I found it to be more unpredictable than concurrent mark&sweep. I'm still waiting for it to be improved.
- runT1ME 15y agoDid you have concurrent collections turned on? It almost always reduces overall throughput of the collector. However in many workloads I expect the G1 to be superior to the current throughput collector....
- smanek 15y agoIs there a better document that explains how the GC works in the latest Java 6 releases (particularly Hotspot)? I'm doing some GC tuning these days - and there seems to be a lot of false/stale information out there. Something this readable, but accurate, would be helpful.
- jonburs 15y agohttp://www.oracle.com/technetwork/java/javase/gc-tuning-6-140523.html http://www.oracle.com/technetwork/java/javase/gc-tuning-6-14... is the canonical source.
- mikopp 15y agoCould you point out what is incorrect? I'm happy to fix it if you can point out the errors and the source of your information. G1 will be great, at least in theory, but it's not production ready. Many of our readers need to tune their GC in WebSphere/WebLogic Environments in production environments, they can't use G1 yet.