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

Examine overhead in java.net.URLClassLoader

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Fix
    • P3
    • None
    • 9
    • core-libs
    • None

    Description

      Brian Goetz says "I was peeking through the URLClassLoader code, and it seems awfully inefficient. If we're so concerned about startup, have we evaluated whether that's a part of the problem? e.g., uses exceptions for control flow, doesn't build maps of what is in each JAR, etc"

      Synchronization in URLClassLoader is also extremely coarse grained. Low hanging fruit?

      This might be helpful when we are attacking the various warmup problems that stem from the huge amounts of classes being generated by Indy.

      I know Claes was looking at stuff like this, so I am assigning it to him.

      Attachments

        Issue Links

          relates to

          Task - A task that needs to be done. JDK-8053904 JVM Warmup: Investigate class installation overhead

          • P3 - Major loss of function.
          • Closed

          Enhancement - null JDK-8061244 Use of stack-less ClassNotFoundException thrown from (URL)ClassLoader.findClass()

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

          Enhancement - null JDK-8057936 java.net.URLClassLoader.findClass uses exceptions in control flow

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

          Enhancement - null JDK-8073497 Lazy conversion of ZipEntry time

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

          Enhancement - null JDK-8057655 Empty delegating URLClassLoader performance is erratic

          • P3 - Major loss of function.
          • Closed

          Enhancement - null JDK-8060130 Simplify the synchronization of defining and getting java.lang.Package

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

          Task - A task that needs to be done. JDK-8053904 JVM Warmup: Investigate class installation overhead

          • P3 - Major loss of function.
          • Closed

          Activity

            People

              redestad Claes Redestad
              lagergren Marcus Lagergren
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: