Re:How Garbage Collection differs in the three big JVMs
by deadc0de on Wednesday May 11, 2011 @03:31PM
(#2538010)
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.
[ Parent
| on HN ]
Re:How Garbage Collection differs in the three big JVMs
by smanek on Wednesday May 11, 2011 @07:03PM
(#2538765)
Is 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.
Re:How Garbage Collection differs in the three big JVMs
by jonburs on Thursday May 12, 2011 @01:03AM
(#2539521)
http://www.oracle.com/technetwork/java/javase/gc-tuning-6-14... is the canonical source.
Re:How Garbage Collection differs in the three big JVMs
by jwr on Wednesday May 11, 2011 @04:39PM
(#2538331)
G1 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.
Re:How Garbage Collection differs in the three big JVMs
by runT1ME on Wednesday May 11, 2011 @05:30PM
(#2538513)
Did 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....
Re:How Garbage Collection differs in the three big JVMs
by mikopp on Thursday May 12, 2011 @02:45AM
(#2539655)
Could 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.