<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ray Tsang on foojay.io - Friends of OpenJDK</title><link>https://foojayio.github.io/website/today/author/saturnism/</link><description>Articles written by Ray Tsang on foojay.io - Friends of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 24 Aug 2020 08:55:22 +0000</lastBuildDate><atom:link href="https://foojayio.github.io/website/today/author/saturnism/index.xml" rel="self" type="application/rss+xml"/><item><title>Container Awareness for Java Developers Today</title><link>https://foojayio.github.io/website/today/container-awareness-for-java/</link><pubDate>Mon, 24 Aug 2020 08:55:22 +0000</pubDate><guid>https://foojayio.github.io/website/today/container-awareness-for-java/</guid><description>&lt;p&gt;When you containerize a Java application, make sure you use a base JDK image that is container-aware (CGroup aware) so that the JDK can allocate memory and CPU counts properly.&lt;/p&gt;
&lt;p&gt;Older versions of JDK (prior to 8u192) may not have container awareness (or may have experimental support that requires explict flags to enable). Older versions of JDK may look at the traditional &lt;code&gt;/proc/meminfo&lt;/code&gt; and &lt;code&gt;/proc/cpuinfo&lt;/code&gt;files for available memory and CPUs. The content of these files reflects the amount of resources of the host/node machine that is running the container, but do not reflect the actual limits assigned to the container (which may be much less).&lt;/p&gt;</description></item></channel></rss>