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

NMT: Tracking compiler memory usage of thread's resource area

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Fixed
    • P4
    • 10
    • 10
    • hotspot
    • b31

    Backports

      Description

        Vladimir Kozlov wrote:
        > Compilers also use a lot thread local ResourceArea -
        > Thread::current()->resource_area() and NEW_RESOURCE_ARRAY() macro.
        > But thread local area is defined as mtThread:

        > Thread() is called from CompilerThread() and we can pass a parameter to
        > indicate user. Or add a virtual method to Thread class to check type of
        > thread.
        >
        > In the past we had compiler local changes to get information how much
        > memory was used during compilation but it was never get pushed. We
        > accessed Arena::_bytes_allocated for that.


        Following email thread for details:
        http://mail.openjdk.java.net/pipermail/hotspot-dev/2017-September/028360.html


        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-8192048 NMT: Tracking compiler memory usage of thread's resource area

            • 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-8196246 NMT: Tracking compiler memory usage of thread's resource area

            • 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-8201043 NMT: Tracking compiler memory usage of thread's resource area

            • 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-8203085 NMT: Tracking compiler memory usage of thread's resource area

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

            Bug - A problem which impairs or prevents the functions of the product. JDK-8204128 NMT might report incorrect numbers for Compiler area

            • P3 - Major loss of function.
            • Resolved

            Activity

              People

                zgu Zhengyu Gu
                zgu Zhengyu Gu
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: