2 Replies Latest reply on Jul 16, 2012 1:36 PM by gboro54

    JBoss 7.1 JVM Tuning

    gboro54

      I am willing to claim I am no JVM tuning expert. I am running into a situation where performance on my local development envrionment with no tuning(except head space increase) is out performaing a mroe powerful box with JBM tunning. Here are my settings for the QA environment we are testing with. I am hoping an expert can help me solidify some of these settings.

       

       

      #Script to start JBoss 7.1.CR1

       

       

      JAVA_OPTS="-server -Djava.awt.headless=true -Xms6144m -Xmx6144m -XX:NewSize=256m -XX:MaxNewSize=256m -XX:PermSize=256m -XX:MaxPermSize=256m  -XX:SurvivorRatio=14 -XX:MaxTenuringThreshold=15 -Xss128k

      -XX:+AggressiveOpts -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled -XX:+UseBiasedLocking -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -Dsun.lang.ClassLoader.allowArraySyntax=true

      -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000"

       

      export JAVA_OPTS=$JAVA_OPTS

      nohup bin/standalone.sh  -c stagging.xml -b <IP> -Djboss.bind.address.management=<IP> &

       

       

       

       

      TIA

        • 1. Re: JBoss 7.1 JVM Tuning
          peterj

          Don't use AggressiveOpts unless you have tested both with and without it. This option exists mainly for running a very specific performance test (SpecJBB). The options used to run that test might not be the best options for you.

           

          When you turn on the CMS collector, it resets various options (such as SurvivorRatio and the tenuring threshold, so you should always turn on CMS before setting other options.

           

          For more details, se my "201" paper at http://www.cmg.org/cgi-bin/search.cgi?q=java+peter+johnson&x=30&y=10

          Also see my "101" paper for ideas on gathering GC data and tuning based on it.

          • 2. Re: JBoss 7.1 JVM Tuning
            gboro54

            Thanks. I removed agressive opts for testing an have moved the CMS to the start of the JAVA_OPTS list.