Elastic JVM for Scalable Java EE Applications Running in Containers       Containers provide much better elasticity and density than VMs, but JVM-based applications are not fully container-ready. The first issue is that HotSpot JVM doesn’t release unused committed heap memory automatically. Second, it is not possible to increase the size of the JVM heap at runtime. To solve these major issues and make JVM more container-friendly, a new patch is implemented for the Garbage-First collector in OpenJDK. This session shares details of what is done and how the added improvements enhance Java resource consumption efficiency.

Subscribe: https://www.youtube.com/user/EclipseFdn
Follow us on Twitter: https://twitter.com/JakartaEE
Like us on Facebook: https://www.facebook.com/JakartaEE/
Join us on LinkedIn: https://www.linkedin.com/groups/13597
Tag us: #JakartaEE
Want more great Eclipse Community webinars? Become a member of our Jakarta Tech Talks Meetup: https://www.meetup.com/jakartatechtalks

Elastic JVM for Elastic Java EE Applications Running in Containers | Jakarta Tech Talks