In an effort to enhance Java efficiency in cloud environments, an OpenJDK proposal is afoot to cut back the dimensions of the JDK (Java Improvement Equipment) by about 25%. The plan requires enabling the jlink software to construct customized runtime pictures with out utilizing the JDK’s JMOD recordsdata.
The JDK Enhancement Proposal (JEP), titled Linking Run-Time Pictures with out JMODs, is motivated by the need to cut back the put in measurement of the JDK on the file system in cloud environments, the place container pictures that embody an put in JDK are often copied over the community from container registries. Lowering the dimensions of the JDK would enhance the effectivity of those operations, the proposal states. The JEP notes that enabling the jlink software to create customized runtime pictures with out utilizing the JDK’s JMOD recordsdata have to be enabled when the JDK is constructed and won’t be enabled by default. Some JDK distributors might select to not allow it.
The proposal explains {that a} full, put in JDK has two important parts: a run-time picture, which serves because the executable Java runtime system, and a set of packaged modules, within the JMOD format, for every module within the runtime picture. JMOD recordsdata are utilized by the jlink software when creating customized runtime pictures. The runtime picture in an entire JDK itself was created from these JMOD recordsdata by way of jlink. Therefore, each class file, native library, configuration file, and different useful resource within the runtime picture is also current in one of many JMOD recordsdata, which is arguably a “large waste of area,” based on the proposal.
