Details

    • Type: Sub Task Sub Task
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Analysis
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-6105JVM Tuning parameters
      KULRICE-12919Performance tuning of KS course search
      KULRICE-6265Add documentation to the KSB Technical Guide on Performance Tuning
      KULRICE-9365Smoke Test proxy JVM param
      KULRICE-10089Performance Tuning Work
      KULRICE-6436Tune ehcache configuration for the various rice modules
      KULRICE-1455tune maintenance document xml strategy
      KULRICE-13571Change Size of performance environments
      KULRICE-13545Cucumber Tests as Documentation and Requirements
      KULRICE-316Document Bamboo configuration settings
    • Rice Module:
      KRAD
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      Determine best JVM setup for KRAD views

        Activity

        Hide
        Heath Kesler (Inactive) added a comment -

        Had an email exchange with Erik about the JVM settings. In the test environment it had

        -XX:+HeapDumpOnOutOfMemoryError
        -XX:+PrintGCDateStamps
        -XX:+PrintGCDetails
        -XX:+PrintHeapAtGC
        -XX:+PrintTenuringDistribution
        -XX:HeapDumpPath=/usr/local/tomcat/logs
        -XX:MaxPermSize=256m
        -Xloggc:/usr/local/tomcat/logs/heap.log
        -Xms512m
        -Xmx2g
        -verbose:gc

        Those GC and Heap logging settings are useful in small controlled environments when you are trying to determine memory utilization and GC algorithms. But they can definitely be a problem when performance testing and production. The GC on 2Gs of memory with those settings will bring the JVM to its knees.

        Erik's recommandation of the follow:

        -XX:HeapDumpPath=/usr/local/tomcat/logs
        -XX:MaxPermSize=256m
        -XX:NewRatio=6
        -Xms512m
        -Xmx2g

        is much better.

        Show
        Heath Kesler (Inactive) added a comment - Had an email exchange with Erik about the JVM settings. In the test environment it had -XX:+HeapDumpOnOutOfMemoryError -XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintHeapAtGC -XX:+PrintTenuringDistribution -XX:HeapDumpPath=/usr/local/tomcat/logs -XX:MaxPermSize=256m -Xloggc:/usr/local/tomcat/logs/heap.log -Xms512m -Xmx2g -verbose:gc Those GC and Heap logging settings are useful in small controlled environments when you are trying to determine memory utilization and GC algorithms. But they can definitely be a problem when performance testing and production. The GC on 2Gs of memory with those settings will bring the JVM to its knees. Erik's recommandation of the follow: -XX:HeapDumpPath=/usr/local/tomcat/logs -XX:MaxPermSize=256m -XX:NewRatio=6 -Xms512m -Xmx2g is much better.
        Hide
        Jessica Coltrin (Inactive) added a comment -

        removing m3 version since these aren't assigned and are unlikely to be done by Monday's m3 release.

        Show
        Jessica Coltrin (Inactive) added a comment - removing m3 version since these aren't assigned and are unlikely to be done by Monday's m3 release.

          People

          • Assignee:
            Unassigned
            Reporter:
            Jerry Neal (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:

              Structure Helper Panel