Oracle has a version 20.2 The GraalVM designed on extensive language disclosure. The current release has innovations for the compile time in the luggage. In addition, the current version fixes errors that have occurred with the Graalvm library libgraal.
In the direction of Java, the update Support for the release of memory brings. When an application enters a stable phase and the compilation becomes inactive, the memory used by Libgraal is output to the operating system. This is apparently reducing the impact of the RSS memory of a GRAAlVM process: An unused compiler consumes no resources. For the enterprise version of the Graalvm, the interference between compiler threads is reduced, using multiple isolates.
The community version of Graalvm 20.2 is based on the OpenJDK versions 1.8th.0_262, and 11.0.8th. Oracles Enterprise version of Graalvm accesses the Oracle JDK version 1.8th.0_261 and 11.0.8th.0.2 Back.
Checking the support for Native Images
The developer team behind Graalvm has worked on the generation of native images that are static with Muslc. Developers using Musl-GCC in the path can produce a native image with –static –libc = Musl that is static with Muslc8 / Code9. Clear information can be found in the documentation.
In addition, the update introduces the function, "Mostly static" Creating native images that are static absorbing everything auber libc. This can create native images that can be used in small docker images. In addition, the development team behind the Virtual Machine has changed the initialization strategy for classes. At the time of creation, it is possible to initialize only a small part of the JDK library.
In addition to updates for the LLVM Runtime, the update brings more bug fixes and overwork for Python. Graalvm 20.1 had already set to more support for Python. Further information about the current release can be found in the Release Notes and on GitHub.