No more Xmx! - Adaptable Heap Sizing for Containerized Java Applications
Conference (INTERMEDIATE level)
Room 8
Score 0.13
Score 0.15
Score 0.16
Score 0.17
The match becomes increasingly accurate as the similarity score approaches zero.

Have you ever run Java in a container? Are you tired of tuning Xmx? If so, this talk is for you! (And even if not, this talk is still for you!)

Come learn about Google's solution to memory management of Java programs inside a container. Currently, the configuration of Java applications is tricky and error-prone; incorrectly-valued flags can have significant performance and cost impact. In practice, the most problematic flag misconfiguration is the maxiumum Java heap size (--Xmx). A new project within Google, called Adaptable Heap Sizing (AHS), boldly removes the need to manually tune and set a maximum heap size, and instead automatically adjusts Java heap usage based on container limits and container usage. Furthermore, AHS improves the stability of Java applications by significantly reducing the likelihood of memory-related runtime errors, while often reducing memory usage as well.

Attend this talk to learn more about Java memory in a container, the history of memory issues at Google, and how we came up with a solution to these problems!

Jonathan Joo

Jonathan is a senior software engineer on the Java Platform Team at Google.

He is currently working on improving the behavior of the JVM Garbage Collector to help save memory and improve stability fleetwide across Google.

Prior to Google, Jonathan also worked on an in-house distributed filesystem at Rubrik, and graduated with a BS in Computer Science from Caltech.

Jonathan hopes that speaking at a conference will help him with performing stand-up comedy one day.