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

Identify and address the likely causes of glibc allocator fragmentation

    XMLWordPrintable

Details

    Description

      glibc can sometimes, especially in case of multi threaded applications, keep certain pages in physical memory even though those pages have already been freed. This can be observed as increase in RSS for programs using glibc allocator.

      The goal of this issue is to identify if there are any allocation patterns in the JVM that can lead to such memory fragmentation and in turn cause increase in RSS for Java applications.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JDK-8193521 glibc wastes memory with default configuration

          • P3 - Major loss of function.
          • Closed

          Enhancement - null JDK-8302264 Improve dynamic compiler threads creation

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

          Enhancement - null JDK-8198756 Lazy allocation of compiler threads

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

          Activity

            People

              jsjolen Johan Sjölen
              poonam Poonam Bajaj Parhar
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated: