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

Add detailed information about PLAB memory usage

    Details

    • Type: Enhancement
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: 9
    • Fix Version/s: 9
    • Component/s: hotspot
    • Labels:
    • Subcomponent:
      gc
    • Resolved In Build:
      b81

      Backports

        Description

         Detecting issues with PLABs, particularly about fragmentation, is currently very limited as the only information received is the current and desired PLAB size.

        It would be interesting to have the following additional information:
        - amount of copied data
        - amount of wasted data due to losing a race when claiming an object to copy
        - amount of wasted data when an object does not fit the PLAB and must be retired (inner fragmentation)
        - amount of wasted data when retiring a PLAB at the end of GC (phase)
        - number of refills requested

        In addition to that, some statistics about the (outer) fragmentation occuring when retiring an allocation region and the number of allocation regions used.

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  tschatzl Thomas Schatzl
                  Reporter:
                  tschatzl Thomas Schatzl
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: