>>I thoguht that it would be a good idea to promote more objects to tenure and take advantage of the CMS collector.
Actually, this is a bad idea based on testing that i haved done. Two reasons:
1) The pauses during CMS and G1 collections (yes, there are pauses - two of them) are about as long as the pause caused by minor collection.
2) While CMS and G1 run, they are using up one entire processor/core at 100% because they are memory and processor intensive. You want those collectors to run as rarely as possible. If you tenure every object that lives through a minor collection, then you are going to run CMS/G1 more often and thus will more often lose the use of a core to process business requests.
See this white paper:
Java Garbage Collection Performance Analysis 201
(I worked with a beta version of G1, so take the stability warnings with a grain of salt)
Thank you for your quick reply Peter. I was wondering if the article that you cite would have the latest command options for G1. I tried some of the optionsthat worked in JDK1.6_14 but they seem to fail with JDK1.6_30.
I am still tryign to log into the web site that shows your article. Does your article delve into the details to take full advantage of the ergonomics of the newest versions of the JDK1.6?
As I mentioned I worked with a beta version of G1 so the white paper (which was written in 2009) doesn't have the latest options. By the way, the white paper that discusses G1 is titled "Reducing Java Garbage Collection Pause Times" (it also covers CMS).
Why are you trying to log onto the web site, you don't need to. The link show take you to a search results page that shows all of my white papers.
That article should be quite informative. Clicking on the link does bring you to the page with a list of your papers but clicking on any of them brings you to a logon and registration page.