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

Exploded image too slow to be usable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P3
    • Resolution: Fixed
    • Affects Version/s: 9
    • Fix Version/s: 9
    • Component/s: infrastructure
    • Labels:
      None
    • Subcomponent:
    • Resolved In Build:
      b139

      Description

      During the build process, we create an exploded image as an interim step before linking the real JDK and JRE images. This exploded image is used both for running certain build tools during the build but is also used by developers when needing a quick build-test cycle since the exploded image is much faster to build incrementally.

      Lately, with newer Jigsaw features, the exploded image has become very slow to run. This is caused by the runtime needing to index all packages in all modules at startup. In a linked image, this data is pregenerated, but in the exploded case, it's not. There have been reports of this taking up to 4-5 seconds on certain configurations.

      To fix this, we can add a new build tool that is run on the exploded image, which updates the module-info.class files with this package index. This will also have the benefit of also speeding up jmod and jlink when run during the build.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                erikj Erik Joelsson
                Reporter:
                erikj Erik Joelsson
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: