To cut back software execution time, Java’s segmented code cache could be prolonged with an non-compulsory “sizzling” code heap to compactly accommodate part of non-profiled strategies, below a draft JDK enhancement proposal now floating within the OpenJDK group. One other success metric of the plan is decreasing the fragmentation of highly-optimized code within the code cache.
By extending Java’s compiler management mechanism to mark sure strategies as sizzling so they might compile into the new code heap, the proposal would separate code that’s recognized to be sizzling, lower fragmentation of chosen code, and scale back the detrimental influence of compiled code hotness scattering on the efficiency of Java functions. It additionally would offer method-context dependent management for putting C2-compiled blobs into the new code heap and supply a foundation for the opportunity of profiling and compacting the code utilizing the digital machine itself.
The new code heap proposal relies on older proposals for a segmented code cache and compiler management. Each are from Java Growth Equipment 9, which was launched in September 2017. Motivating the brand new proposal is the premise that sparse sizzling code is slower. Some functions could lose their efficiency as a result of large JVM code cache. This occurs below sure circumstances comparable to quite a lot of code being JIT-compiled, the presence of an enormous quantity of sizzling code, and sizzling code being scattered all through the code cache.
The CPU itself imposes penalties for executing giant quantities of scattered code, the proposal states. On programs the place this drawback is critical, it can’t be solved by different means, comparable to giant pages. The diploma of the slowdown will depend on the quantity of sizzling code, the sparseness of that code, and the processor sort.
The proposal additionally emphasizes that not all compiled code is known as ceaselessly on a regular basis and that co-locating sizzling code utilizing profile info can increase efficiency. It additionally is feasible to boost compilation coverage for warm code for higher efficiency and to carry out extra aggressive sweeping of colder code to scale back code cache.
The new code heap proposal has not been designated for a selected launch of Java. The present launch, JDK 22, was launched final week whereas JDK 23 is due in September. JDK 23 could be a possible goal for the new code heap proposal, though the plan may slip out to an extra launch.
Copyright © 2024 IDG Communications, Inc.
