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

Shenandoah should report "committed" as capacity

    Details

    • Subcomponent:
      gc
    • Resolved In Build:
      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

            There are no Sub-Tasks for this issue.

              Activity

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved: