Announcement

Collapse
No announcement yet.

[SOLVED] aggressive heap on Linux

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • [SOLVED] aggressive heap on Linux

    We've been setup an OTM instance on Red Hat Linux (for the first
    time) and
    we are using following setup (with aggressive heap and
    Xgcprio:throughput).
    What do you think of this setup? Is it recommending to use the
    aggressive
    heap setting?
    We also setup the Xverbose to analyse the JVM behaviour in HPJTune,
    but the
    output coming from JRockit JDK is different from the one coming from
    Sun
    JDK and is not readable in HPJTune. What's wrong with our setup to
    get it
    readable in HPJTune?
    # Java Additional Parameters
    wrapper.java.additional.1=-jrockit
    wrapper.java.additional.2=-Xms2500m
    wrapper.java.additional.3=-Xmx2500m
    wrapper.java.additional.4=-XXaggressive:memory
    wrapper.java.additional.5=-Xgcprio:throughput
    wrapper.java.additional.6=-Xverbose:memory,gc
    wrapper.java.additional.7=-Xnoclassgc
    wrapper.java.additional.8=-Dglog.home=%GLOG_HOME%/glog/config
    wrapper.java.additional.9=-Duser.home=%GLOG_HOME%/glog/config
    wrapper.java.additional.10=-Djava.io.tmpdir=%GLOG_HOME%/temp
    wrapper.java.additional.11=-Djava.awt.headless=true
    wrapper.java.additional.12=-Djava.security.auth.login.config=%GLOG_HOME%/glog/config/gc3_jaas.config
    wrapper.java.additional.13=-Dweblogic.Name=gc3-fikylx20
    wrapper.java.additional.14=-Dbea.home=/opt/otm/bea
    wrapper.java.additional.15=-Dweblogic.home=%WL_HOME%/server
    wrapper.java.additional.16=-Dweblogic.management.username=system
    wrapper.java.additional.17=-Dweblogic.management.password=%WL_PW%
    wrapper.java.additional.18=-Dweblogic.ProductionModeEnabled=true
    wrapper.java.additional.19=-Dweblogic.management.discover=false
    wrapper.java.additional.20=-Djava.security.policy=%WL_HOME%/server/lib/weblogic.policy
    wrapper.java.additional.21=-Xss256k
    wrapper.java.additional.22=-Xverboselog:/opt/otm/gc3v55_devp_webapp/logs/weblogic/tracejava.vgc
    wrapper.java.additional.23=-XverboseTimeStamp
    We are using 2 CPUS 2.4Ghz Xeon P-IV.

    Regards,

    Kristof Stevens
    OTM Technical consultant

  • #2
    Re: aggressive heap on Linux

    Additional information :

    2 CPUs on Red Hat AS/ES 4.0 64-bit

    CPU0: Intel(R) Xeon(R) CPU 5140 @ 2.33GHz stepping 06
    CPU1: Intel(R) Xeon(R) CPU 5140 @ 2.33GHz stepping 06


    Comment


    • #3
      Re: aggressive heap on Linux

      Kristof,

      I don't know of a way to regularize the Verbose GC output from JRockit. While I was working at G-Log, we had to modify our GC graphing scripts to specifically map against JRockit's output. In fact, we had to do the same for the IBM JDK. One option may be a Perl or Ruby script to convert the GC info into a Sun JDK format.

      The best option I've found, so far, has been BEA's management tools, including the JRockit Console and Mission Control.

      Just for reference, I've found the following tools useful for diagnosing JVM memory issues with the Sun JDK, though I don't know if any are compatible with JRockit:BTW, the best CPUs I've seen in use with OTM and other Java application servers are the Intel 5160 and E5355 CPUs.

      Hope this helps!
      --Chris

      Comment

      Working...
      X