Heya, I've given a MXDU presentation on that stuff in 2005 (<http://www.bloginblack.de/archives/000630.cfm>) - Slide 34 actually has a few good references to read up on the topic if you like.
Basically - I can't agree more to Stephen - JVM settings can ruin your performance if done wrongly and they can improve your performance as soon as your systems architecture derives from the standard environment. Not sure which JVM you're on, here's another good read for 1.4.2: <http://java.sun.com/docs/hotspot/gc1.4.2/> Cheers Kai >On May 12, 12:07 pm, "Steve Onnis" <[EMAIL PROTECTED]> wrote: >> Can someone shed some light on what the JVM Heap Size is actually meant to >> do? For example, if I set it to the max heap size of 512mb, does that mean >> that the actual memory consumed by the jrun.exe should not exceed 512mb ? >> >> I have an issue where if the jrun.exe memory usage goes over say 600mb the >> cf server just dies and stops responding unless I restart the cf server and >> its driving me bananas. >> >> Anyone got any ideas? > >Is this single-processor, multi-processor? Have you got any settings >for Garbage Collection (concurrent,parallel copying, parallel >scaveging?) >I got a copy of "CFMX troubleshooting and Optimization" by some Nu >Zeelun dude (hello Grant) and it says >"If you are using more than one processor than the selecting the >correct collector can have a major impact on JVM" > >regards, >Stephen >> >> Steve >> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
