To boost Java performance in cloud settings, an OpenJDK initiative seeks to reduce the size of the heap by approximately 25% for increased scalability. The plan requires enabling the jlink Software designed to create tailored runtime images without leveraging the JDK’s resources.
To improve scalability in cloud environments, this JDK Enhancement Proposal (JEP) aims to reduce the footprint of the installed JDK on the file system by minimizing the duplication of large JDK images across containers in container registries. According to the proposal, scaling down the JDK would improve the efficiency of these operations. The Joint Editorial Process (JEP) observes that the activation of jlink Software to generate personalized runtime images without relying on the JDK’s JMOD files should be enabled during the JDK build process, but will not be enabled by default. Certain JDK distributors may choose not to permit this option.
The proposal outlines that a complete JDK comprises two primary components: a runtime environment, serving as the executable Java runtime system, and a collection of packaged modules, each contained within the runtime environment. JMOD files are utilized by the jlink Software enabling users to generate tailored runtime images. The runtime image within an entire JDK itself was created from these JMOD records by using jlink. As a result, every class file, native library, configuration file, and additional valuable resource within the runtime environment is stored in one of several JMOD files, raising concerns about the potential “waste of space”.
