On 5/26/06, Dan Wilson <[EMAIL PROTECTED]> wrote:
So to the layperson, Explicit Garbage collection would infer a complete
*imply* People infer, situations imply. Sorry, grammatical hot button. Normally Java applications let the JVM figure out when and how it needs to handle garbage collection. That's one of the great benefits of a managed language. However, Java has always allowed applications to request garbage collection be performed. Back in the day, the JVM wasn't as sophisticated and sometimes applications needed to force it to run the collector. A lot of Java developers got into the habit of calling the garbage collector explicitly. Nowadays, the GC in Java is much more sophisticated and it's pretty much a cardinal rule that you should never call the GC explicitly now - the JVM is much smarter about its memory usage than you are :) Since there are still a lot of bad Java applications out there that call the GC directly, the JVMs have an option to disable explicit GC so you can prevent that bad behavior. I would disable explicit GC as a matter of course on anything that is even remotely high-traffic. I would also spend some time looking at the various GC algorithms and ratios between the various heap areas. Sun has some great material on their site about tuning garbage collection. Be warned, it's dense, very dense - and very, very technical for the most part. There are, unfortunately, no silver bullets in terms of settings for the JVM. What Mike and Doug end up on for Doug's site may not be best for you - and if Doug's server's load / applications change, it'll need tweaking again. The default JVM settings provided with CFMX are a good middle ground for most situations and set a reasonable baseline for tuning. -- Sean A Corfield -- http://corfield.org/ Got frameworks? "If you're not annoying somebody, you're not really alive." -- Margaret Atwood -- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/
