Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8222409

Committed Memory and Available memory in Heap is same in JDK 1.8.0_202

    Details

    • Subcomponent:
      gc
    • CPU:
      x86_64
    • OS:
      linux

      Description

      A DESCRIPTION OF THE PROBLEM :
      Our Cloud application(Stratos) is deployed with the JDK 1.8.0_202 post that we are observing unusual behavior of Heap.
      We have allocated 2GB Heap size and given the NewRatio=1. However we are observing that Eden Space,Survivor space is having only 21M committed memory out of 1GB Available memory.
      The Old JDK 1.8.0_101 doesnt have this issue and the Committed memory is equal to Available memory.
      Our application doesnt have any Memory leak with the OLD JDK.
      Issue is coming only with the new JDK(1.8.0_202)
      As a result of less Committed memory we have frequent GC happenings

      Current Version
      • java_buildpack_latest [ java-buildpack-offline-v4.19-c0.13.0.zip]
      • java version: OpenJDK 64-Bit Server VM 1.8.0_202 Oracle Corporation


      -XX:+UseCompressedOops
      -XX:+UseParNewGC
      -XX:NewRatio=1
      -XX:+UseConcMarkSweepGC
      -XX:+CMSClassUnloadingEnabled
      -XX:+CMSScavengeBeforeRemark
      -XX:+DisableExplicitGC
      -XX:CMSInitiatingOccupancyFraction=75
      -XX:+UseCMSInitiatingOccupancyOnly
      -Xmx2380279K
      -Xss1M
      -XX:ReservedCodeCacheSize=240M
      -XX:MaxDirectMemorySize=10M
      -XX:MaxMetaspaceSize=253448K


      FREQUENCY : always


        Attachments

          Activity

            People

            • Assignee:
              fmatte Fairoz Matte
              Reporter:
              webbuggrp Webbug Group
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: