JAVA 10 Improvements to Garbage collection
Posted By : Arun Singh | 23-Apr-2018
Java JDK 10 that focus on improving the current Garbage Collection(GC) elements. The first Garbage collector(GC) Interface is JEP 304. It's introducing a clean garbage collector interface to help improve the source code isolation of different garbage collectors.
In current Java version, there are bits and scrap of GC source files scattered all over the HotSpot sources. When developer implementing a new garbage collector since developers have to know where to look for those source files. The one major objective of this JEP is to provide better modularity for HotSpot internal GC code, have a cleaner GC interface and make it easier to implement new collectors.
The second objective of JEP that is scheduled for Java 10 is Parallel Full GC for G1 (JEP 307), which puts its focus on improving G1 worst-case latencies, by making the full GC parallel. In Java 9 G1 was made the default GC, and the goal of this JEP is to make G1 parallel as well.
Some features that are scheduled for Java 10:
JEP 312 Thread Local Handshakes:- This feature introducing a new approach to execute a callback on threads, so it will be both feasible and cheap to stop individual threads and not just all threads or none.
JEP 316 Heap Allocation:– The VM hotSpot to allocating the java object heap on an different memory device.
JEP 314 Additional Unicode:- The feature increasing the java.util.Local and its related API's, to make it feasible to implement additional Unicode extensions of language tag syntax.
JEP 317 Experimental Java-Based JIT Compiler:– The Oracle wants to implement its Java JIT compiler, Graal, to be used as an empirical JIT compiler on the Linux/x64 platform.
JEP 319 Root Certificates:– The main target is to open source the root certificates in Oracle’s Java SE
Root Certification Authority (CA) program, making OpenJDK builds extra tempting to developers. It also objective to decrease the difference between the OpenJDK and Oracle JDK builds.
JEP 296 Consolidate the JDK Forest into a Single Repository:– The main target of this JEP is to do some housekeeping and merge the big repositories of the JDK forest into a single repository.
JEP 313 Remove the Native-Header Generation Tool (javah):– This one is transparent and to the point – remove the javah tool from the JDK.
Cookies are important to the proper functioning of a site. To improve your experience, we use cookies to remember log-in details and provide secure log-in, collect statistics to optimize site functionality, and deliver content tailored to your interests. Click Agree and Proceed to accept cookies and go directly to the site or click on View Cookie Settings to see detailed descriptions of the types of cookies and choose whether to accept certain cookies while on the site.
About Author
Arun Singh
Arun is a MEAN stack developer. He has a fastest and efficient way of problem solving techniques. He is very good in JavaScript and also have a little bit knowledge of Java and Python.