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

Monitor deflation prolong safepoints

    Details

    • Type: Enhancement
    • Status: In Progress
    • Priority: P3
    • Resolution: Unresolved
    • Affects Version/s: 8u72, 9
    • Fix Version/s: 15
    • Component/s: hotspot
    • Subcomponent:
    • Understanding:
      Fix Understood
    • CPU:
      generic
    • OS:
      generic

      Description

      In applications with non-trivial amounts of lock contention the time to deflate idle monitors can prolong safepoints by a non-trivial amount.

      Today monitors are deflated by the VM thread in the beginning of every safepoint. In JDK-7021979 it was observed that 250,000 monitors can easily take up to 8ms to process. The 250,000 monitors were created artificially using a small java program.

      At Twitter we have seen programs with more than 600,000 monitors and 6500 threads. The ratio between threads and monitors allocated is less than 10% of the MAXPRIVATE (1024) private monitors per thread, suggesting these program do not suffer from the issue reported in JDK-7021979.

        Attachments

          Issue Links

          blocks

          Enhancement - null JDK-8225631 Consider replacing muxAcquire/Release with PlatformMonitor

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

          Enhancement - null JDK-7021979 rapid sustained monitor circulation causes asymptotic increase in # of extant monitors

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

          Enhancement - null JDK-8149442 MonitorInUseLists should be on by default, deflate idle monitors taking too long

          • P3 - Major loss of function.
          • Resolved

          Enhancement - null JDK-8180175 ObjectSynchronizer only needs to iterate in-use monitors

          • P3 - Major loss of function.
          • Resolved

          Enhancement - null JDK-8180932 Parallelize safepoint cleanup

          • P3 - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JDK-8221616 gtest/GTestWrapper.java crashed due to SIGSEGV on Linux-X64

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

          Enhancement - null JDK-8184751 Provide thread pool for parallel safepoint cleanup

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

            Activity

              People

              • Assignee:
                dcubed Daniel Daugherty
                Reporter:
                cvarming Carsten Varming
              • Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated: