JVM-based applications are not fully container-ready, so cannot benefit from elasticity and density of this technology.
The first issue is that HotSpot JVM doesn’t release unused committed Heap memory automatically.
Secondly, it is not possible to increase the size of JVM Heap in runtime. To solve these two major issues and make JVM more container friendly, a new patch is implemented for the Garbage First collector in OpenJDK 9.
Find out more details what is done and how the added improvements improve resource consumption efficiency.
Publisher: Jelastic Cloud
You can watch this video also at the source.