The plan, made public by Ioi Lam of Oracle in an OpenJDK neighborhood RFC last month, lines up with Job Leyden, an effort to enhance start-up times for Java applications as well as times to peak efficiency and program footprints. Lam noted that Job Leyden is likely to make substantial usage of archived Java heap objects.Goals of the CDS
enhancement strategy include uniform assistance of CDS for all collectors and lessening the code needed for each collector to support CDS. CDS itself is meant to minimize application startup times, in specific for smaller sized applications. CDS is supported just with the Java HotSpot client VM and just with the serial garbage collector.The CDS enhancement plan requires: Eliminating the G1 garbage man reliance for writing the archive heap
- ; a working prototype currently has been established. Combining the archive heap into an adjoining block. The intent is to make it simple to mmap(memory map)the archive load into various collectors. Elimination of G1 archive area types also is planned as part of this step. Execution of mmap of the archive area for other collectors. The execution is expected to be relatively basic.
- Since Java Advancement Kit (JDK)20, which is due as a production release in March, implementers of the plan need to handle limitations including CDS archive disposing only being supported by the G1 collector, G1 having a special allotment routine for space in the stack, and mmap supported only in G1.Providing the motivation for the CDS proposition was a Java development plan to have consistent APIs for utilizing archived areas. That proposal was launched this previous November.
Copyright © 2023 IDG Communications, Inc. Source