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

Shenandoah should report "committed" as capacity

    XMLWordPrintable

Details

    • gc
    • b16

    Backports

      Description

        Shenandoah resizes the heap by (un)committing the individual regions. Therefore, the true heap capacity is the "committed" size, not the maximum possible capacity. Currently, gc logs misreport the heap size, for example with -Xms1g -Xmx4g:

        GC(2) Concurrent marking 183M->183M(4096M) 2.243ms

        Notice "(4096M)", which is not the actual memory taken by committed heap.

        Attachments

          Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8222475 Shenandoah should report "committed" as capacity

            • P4 - Minor loss of function, or other problem where easy workaround is present.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8222619 Shenandoah should report "committed" as capacity

            • P4 - Minor loss of function, or other problem where easy workaround is present.
            • Resolved
            relates to

            Enhancement - null JDK-8222186 Shenandoah should not uncommit below minimum heap size

            • P3 - Major loss of function.
            • Resolved

            Activity

              People

                shade Aleksey Shipilev
                shade Aleksey Shipilev
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: