In an effort to enhance Java efficiency in cloud environments, an OpenJDK proposal is afoot to scale back the scale of the JDK (Java Improvement Equipment) by about 25%. The plan requires enabling the jlink instrument to construct customized runtime pictures with out utilizing the JDK’s JMOD information.
The JDK Enhancement Proposal (JEP), titled Linking Run-Time Pictures with out JMODs, is motivated by the need to scale back the put in dimension of the JDK on the file system in cloud environments, the place container pictures that embrace an put in JDK are steadily copied over the community from container registries. Lowering the scale of the JDK would enhance the effectivity of those operations, the proposal states. The JEP notes that enabling the jlink instrument to create customized runtime pictures with out utilizing the JDK’s JMOD information should be enabled when the JDK is constructed and won’t be enabled by default. Some JDK distributors could select to not allow it.
The proposal explains {that a} full, put in JDK has two essential elements: 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 information are utilized by the jlink instrument when creating customized runtime pictures. The runtime picture in a whole JDK itself was created from these JMOD information through 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 information, which is arguably a “large waste of area,” based on the proposal.
