With large amounts of RAM allocated to the JVM heap Garbage Collection can become a lengthy process. Since the JVM essentially stops all processing during the default GC process, larger heap sizes can produce short stops (pauses) in your CFML processing while the JVM runs the GC process.
You can adjust your GC type to help alleviate this with larger heaps. For example, check out the JVM options -XX:+UseParallelGC, -XX:+UseConcMarkSweepGC, -XX:+UseTrainGC. These are different types of collectors which have different use-cases, so it's important to understand them in order to identify which one is more appropriate to your situation. A quick Google search turned up this for me: http://www.oracle.com/technetwork/java/gc-tuning-5-138395.html Which covers the different GC types a bit. Hope this helps! Warm Regards, Jordan Michaels On 01/12/2012 01:40 PM, Brook Davies wrote: > > Quick Question. On our new server we have lots of ram (32 gigs). Its running > CF 9 Standard 64 bit. Is there any downside to allocating 12 gigs of ram to > CF? > > > > Brook > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:349485 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
