There are few setting you are missing. -Xms512m This sets the min heap size to the same size as the max heap size. The JVM is designed to auto size up from the min to max as needed however this can lead to problems on occasion. So far the best minds on this subject still recommend setting the min to equal the max.
-XX:PermSize=192 This is for the memory space inside the JVM. new gen/old gen/eden/ etc. You can read all about the memory usage at Sun's (er Oracle's) website. In any case it is good to set the min size to the same as the max size for the same reasons above. This settings does that. Next are the GC intervals. These are by default not set so the JVM runs a GC once per minute. There are many reasons why this can and won't work depending on your setup, application memory usage and server load. In any case I've found that the following settings are a good start for setting the GC interval. The new setting is for every 10 minutes. -Dsun.rmi.dgc.client.gcInterval=600000 -Dsun.rmi.dgc.server.gcInterval=600000 Also remember that 64bit does use more memory to start with so even if your app(s) ran fine with just 512 on your 32bit server it's possible and even likely that you will need to increase or even double the memory setting. Just make sure you have enough physical RAM in the server and available for JVM usage. Enjoy, Wil Genovese Sr. Web Application Developer/ Systems Administrator Wil Genovese Consulting [email protected] www.trunkful.com On Jul 12, 2010, at 5:46 PM, Kris Jones wrote: > > It's as default as it gets. No changes from initial install at all: > > An enterprise server CF9 hf1: > > java.args=-server -Xmx512m -Dsun.io.useCanonCaches=false > -XX:MaxPermSize=192m -XX:+UseParallelGC -Xbatch > -Dcoldfusion.rootDir={application.home}/ > -Djava.security.policy={application.home}/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/coldfusion.policy > -Djava.security.auth.policy={application.home}/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/neo_jaas.policy > > A standard server CF9 hf1: > > java.args=-server -Xmx512m -Dsun.io.useCanonCaches=false > -XX:MaxPermSize=192m -XX:+UseParallelGC -Xbatch > -Dcoldfusion.rootDir={application.home}/../ > -Djava.security.policy={application.home}/../lib/coldfusion.policy > -Djava.security.auth.policy={application.home}/../lib/neo_jaas.policy > -Dcoldfusion.classPath={application.home}/../lib/updates,{application.home}/../lib,{application.home}/../gateway/lib/,{application.home}/../wwwroot/WEB-INF/cfform/jars,{application.home}/../wwwroot/WEB-INF/flex/jars > -Dcoldfusion.libPath={application.home}/../lib > > Cheers, > Kris > > > On Mon, Jul 12, 2010 at 5:16 PM, Wil Genovese <[email protected]> wrote: >> >> Please post your JVM config line from jvm.config >> >> I can most likely give you the pointers you need once I see your existing >> config arguments. >> > >>> >>> We've been running into some issues while testing a new deployment. >>> Servers are CF9 (hf1) on Win2k8 64-bit. Also seeing same problems on >>> developer machines running Win7 64-bit, and WinXP (32-bit). We're >>> seeing the problem on both CF9 Standard as well as CF9 Enterprise. >>> >>> We're having trouble getting the GC to maintain a happy state, service >>> climbs and climbs, and eventually kacks the server. Wondering if any >>> of the following suggestions for GC settings etc., still apply for >>> CF9. >>> http://www.coldfusionmuse.com/index.cfm/2005/10/28/jvm.gc >>> http://www.petefreitag.com/articles/gctuning/ >>> >>> Did find this, which shows his solution, but no good discussion about >>> setup based on server config: >>> http://forums.adobe.com/thread/642057?tstart=0 >>> >>> And this one discusses 64-bit implementation, but again, no real >>> guidelines for how to tune. >>> http://groups.google.com/group/cfaussie/browse_thread/thread/3932bce486621abe/8b37ea8cbe0384b6?pli=1 >>> >>> And on GC itself: >>> http://www.softwaresecretweapons.com/jspwiki/thelastjavagarbagecollectionguideyouwilleverneed >>> >>> Are there other resources that detail JVM args, GC settings, versions, >>> etc., as relates to CF9? Is it advisable to change the GC type? >>> >>> CF9 ships with 6.0_14, which doesn't exhibit the class loader bug. We >>> are seeing some mem lost when passing very large strings between >>> objects. This is resolved if we package the strings inside of structs >>> (pass by ref vs. pass by val), or write the process old-school. But, >>> honestly, is that a solution? We've implemented a check for var >>> scoping errors across the board, and have made sure that the output >>> attribute on every function definition is there and set to either true >>> or false (not left blank, or undefined). >>> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:335279 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
