Skip to main content
J
jfrobishow
Known Participant
May 19, 2010
Question

Help me stabilize this jRun configuration (CF9/Win2k3/IIS6)

  • May 19, 2010
  • 1 reply
  • 2358 views
Please download the attached file to view this post
    This topic has been closed for replies.

    1 reply

    A
    Anonymous
    June 29, 2010

    Try these modified arguments in the jvm.config file...

    java.args=-server -Xms768m -Xmx896m -Dsun.io.useCanonCaches=false -XX:PermSize=192m -XX:MaxPermSize=512m -XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=90 -XX:+UseParallelGC -Dcoldfusion.rootDir={application.home}/ -verbose:gc -Xloggc:c:/Jrun4/logs/gc/gcInstance1b.log

    After the CF restart and after you have run for a while (few hours) can you post the last few entries in the gcInstance1b.log?

    CFWhisperer http://www.cfwhisperer.com/

    J
    jfrobishowAuthor
    Known Participant
    July 2, 2010

    Hi! Thanks for the reply,

    After much googling we've finally found a stable configuration.

    java.args=-server -Xmx768m -Xss64k -Dsun.io.useCanonCaches=false -XX:MaxPermSize=512m -XX:+UseParallelGC -Dcoldfusion.rootDir={application.home}/ -verbose:gc -Xloggc:c:/Jrun4/logs/gc/gcInstance1b.log

    I tried playing with the survivor ratio but came back to the default when I didn't notice much improvement.  In the end what did it (pretty sure) is -Xss to reduce the requests size living on the stack.  Our large initial heap, perm + overhead combined with the default request size was causing the JVM to go over and blow up I think.

    We've been stable for over a month now, the next step for us is to reduce the MaxPermSize a little at a time to find our optimal range.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices