Generated from commit: 1ec729b20c38c33f79db3db9ac838b28b77f8a04
diff --git a/search/search_index.json b/search/search_index.json
index c92bfb6..ca615d9 100644
--- a/search/search_index.json
+++ b/search/search_index.json
@@ -4757,17 +4757,17 @@
},
{
"location": "/xxusecontainersupport/",
- "text": "-XX:[+|-]UseContainerSupport\n\n\n(Linux\u2122 only)\n\n\nIf your application is running in a container that imposes a memory limit, and you want the VM to allocate a larger fraction of memory to the Java heap, set the \n-XX:+UserContainerSupport\n option.\n\n\nSyntax\n\n\n -XX:[+|-]UseContainerSupport\n\n\n\n\n\n\n\n\n\n\n\nSetting\n\n\nEffect\n\n\nDefault\n\n\n\n\n\n\n\n\n\n\n-XX:-UseContainerSupport\n\n\nDisable\n\n\nyes\n\n\n\n\n\n\n-XX:+UseContainerSupport\n\n\nEnable\n\n\n\n\n\n\n\n\n\n\nWhen using container technology, applications are typically run on their own and do not need to compete for memory. The OpenJ9 VM detects when it is running inside a container that imposes a memory limit, and if \n-XX:+UserContainerSupport\n is set, adjusts the maximum Java heap size appropriately.\n\n\nThe following table shows the values that are used when \n-XX:+UserContainerSupport\n is set:\n\n\n\n\n\n\n\n\nContainer memory limit \n<size>\n\n\nMaximum Java heap size\n\n\n\n\n\n\n\n\n\n\nLess than 1 GB\n\n\n50% \n<size>\n\n\n\n\n\n\n1 GB - 2 GB\n\n\n<size>\n - 512 MB\n\n\n\n\n\n\nGreater than 2 GB\n\n\n75% \n<size>\n\n\n\n\n\n\n\n\nThe default heap size for containers takes affect only when the following conditions are met:\n\n\n\n\nThe application is running in a container environment.\n\n\nThe memory limit for the container is set.\n\n\nThe \n-XX:+UseContainerSupport\n option is specified on the command line, which is expected to be the default in a future release.\n\n\n\n\nWhen \n-XX:MaxRAMPercentage\n or \n-XX:InitialRAMPercentage\n are used with \n-XX:+UseContainerSupport\n, the corresponding heap setting is determined based on the memory limit of the container. For example, to set the maximum heap size to 80% of the container memory, specify the following options:\n\n\n-XX:+UseContainerSupport -XX:MaxRAMPercentage=80",
+ "text": "-XX:[+|-]UseContainerSupport\n\n\n(Linux\u2122 only)\n\n\nIf your application is running in a container that imposes a memory limit, the VM allocates a larger fraction of memory to the Java heap. To turn off this behavior, set the \n-XX:-UserContainerSupport\n option on the command line.\n\n\nSyntax\n\n\n -XX:[+|-]UseContainerSupport\n\n\n\n\n\n\n\n\n\n\n\nSetting\n\n\nEffect\n\n\nDefault\n\n\n\n\n\n\n\n\n\n\n-XX:-UseContainerSupport\n\n\nDisable\n\n\n\n\n\n\n\n\n-XX:+UseContainerSupport\n\n\nEnable\n\n\nyes\n\n\n\n\n\n\n\n\nWhen using container technology, applications are typically run on their own and do not need to compete for memory. The OpenJ9 VM detects when it is running inside a container that imposes a memory limit, and adjusts the maximum Java heap size appropriately.\n\n\nThe following table shows the values that are used when \n-XX:+UserContainerSupport\n is set:\n\n\n\n\n\n\n\n\nContainer memory limit \n<size>\n\n\nMaximum Java heap size\n\n\n\n\n\n\n\n\n\n\nLess than 1 GB\n\n\n50% \n<size>\n\n\n\n\n\n\n1 GB - 2 GB\n\n\n<size>\n - 512 MB\n\n\n\n\n\n\nGreater than 2 GB\n\n\n75% \n<size>\n\n\n\n\n\n\n\n\nThe default heap size for containers takes affect only when the following conditions are met:\n\n\n\n\nThe application is running in a container environment.\n\n\nThe memory limit for the container is set.\n\n\nThe \n-XX:+UseContainerSupport\n option is set, which is the default behavior.\n\n\n\n\nTo prevent the VM adjusting the maximum heap size when running in a container, set \n-XX:-UseContainerSupport\n.\n\n\nWhen \n-XX:MaxRAMPercentage\n or \n-XX:InitialRAMPercentage\n are used with \n-XX:+UseContainerSupport\n, the corresponding heap setting is determined based on the memory limit of the container. For example, to set the maximum heap size to 80% of the container memory, specify the following options:\n\n\n-XX:+UseContainerSupport -XX:MaxRAMPercentage=80",
"title": "-XX:[+|-]UseContainerSupport"
},
{
"location": "/xxusecontainersupport/#-xx-usecontainersupport",
- "text": "(Linux\u2122 only) If your application is running in a container that imposes a memory limit, and you want the VM to allocate a larger fraction of memory to the Java heap, set the -XX:+UserContainerSupport option.",
+ "text": "(Linux\u2122 only) If your application is running in a container that imposes a memory limit, the VM allocates a larger fraction of memory to the Java heap. To turn off this behavior, set the -XX:-UserContainerSupport option on the command line.",
"title": "-XX:[+|-]UseContainerSupport"
},
{
"location": "/xxusecontainersupport/#syntax",
- "text": "-XX:[+|-]UseContainerSupport Setting Effect Default -XX:-UseContainerSupport Disable yes -XX:+UseContainerSupport Enable When using container technology, applications are typically run on their own and do not need to compete for memory. The OpenJ9 VM detects when it is running inside a container that imposes a memory limit, and if -XX:+UserContainerSupport is set, adjusts the maximum Java heap size appropriately. The following table shows the values that are used when -XX:+UserContainerSupport is set: Container memory limit <size> Maximum Java heap size Less than 1 GB 50% <size> 1 GB - 2 GB <size> - 512 MB Greater than 2 GB 75% <size> The default heap size for containers takes affect only when the following conditions are met: The application is running in a container environment. The memory limit for the container is set. The -XX:+UseContainerSupport option is specified on the command line, which is expected to be the default in a future release. When -XX:MaxRAMPercentage or -XX:InitialRAMPercentage are used with -XX:+UseContainerSupport , the corresponding heap setting is determined based on the memory limit of the container. For example, to set the maximum heap size to 80% of the container memory, specify the following options: -XX:+UseContainerSupport -XX:MaxRAMPercentage=80",
+ "text": "-XX:[+|-]UseContainerSupport Setting Effect Default -XX:-UseContainerSupport Disable -XX:+UseContainerSupport Enable yes When using container technology, applications are typically run on their own and do not need to compete for memory. The OpenJ9 VM detects when it is running inside a container that imposes a memory limit, and adjusts the maximum Java heap size appropriately. The following table shows the values that are used when -XX:+UserContainerSupport is set: Container memory limit <size> Maximum Java heap size Less than 1 GB 50% <size> 1 GB - 2 GB <size> - 512 MB Greater than 2 GB 75% <size> The default heap size for containers takes affect only when the following conditions are met: The application is running in a container environment. The memory limit for the container is set. The -XX:+UseContainerSupport option is set, which is the default behavior. To prevent the VM adjusting the maximum heap size when running in a container, set -XX:-UseContainerSupport . When -XX:MaxRAMPercentage or -XX:InitialRAMPercentage are used with -XX:+UseContainerSupport , the corresponding heap setting is determined based on the memory limit of the container. For example, to set the maximum heap size to 80% of the container memory, specify the following options: -XX:+UseContainerSupport -XX:MaxRAMPercentage=80",
"title": "Syntax"
},
{
diff --git a/sitemap.xml b/sitemap.xml
index 460086f..17da7d3 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -12,7 +12,7 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/introduction/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -21,19 +21,19 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/version0.10/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/version0.9/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/version0.8/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -42,7 +42,7 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/gc/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -50,7 +50,7 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/jit/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -58,7 +58,7 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/aot/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -66,7 +66,7 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/shrc/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -75,25 +75,25 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/diag_overview/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/dump_javadump/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/dump_heapdump/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/dump_systemdump/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -103,19 +103,19 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/cmdline_specifying/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/cmdline_general/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/cmdline_migration/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -143,19 +143,19 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/tool_jdmpview/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/tool_traceformat/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/tool_builder/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -165,31 +165,31 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/openj9_support/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/openj9_defaults/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/openj9_directories/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/messages_intro/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/env_var/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -198,7 +198,7 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/legal/</loc>
- <lastmod>2018-10-11</lastmod>
+ <lastmod>2018-10-16</lastmod>
<changefreq>daily</changefreq>
</url>
diff --git a/xxusecontainersupport/index.html b/xxusecontainersupport/index.html
index 0874937..b412b89 100644
--- a/xxusecontainersupport/index.html
+++ b/xxusecontainersupport/index.html
@@ -2853,7 +2853,7 @@
<h1 id="-xx-usecontainersupport">-XX:[+|-]UseContainerSupport</h1>
<p><strong>(Linux™ only)</strong></p>
-<p>If your application is running in a container that imposes a memory limit, and you want the VM to allocate a larger fraction of memory to the Java heap, set the <code>-XX:+UserContainerSupport</code> option.</p>
+<p>If your application is running in a container that imposes a memory limit, the VM allocates a larger fraction of memory to the Java heap. To turn off this behavior, set the <code>-XX:-UserContainerSupport</code> option on the command line.</p>
<h2 id="syntax">Syntax</h2>
<div class="codehilite"><pre><span></span> -XX:[+|-]UseContainerSupport
</pre></div>
@@ -2871,16 +2871,16 @@
<tr>
<td><code>-XX:-UseContainerSupport</code></td>
<td>Disable</td>
-<td align="center"><i class="fa fa-check" aria-hidden="true"></i><span class="sr-only">yes</span></td>
+<td align="center"></td>
</tr>
<tr>
<td><code>-XX:+UseContainerSupport</code></td>
<td>Enable</td>
-<td align="center"></td>
+<td align="center"><i class="fa fa-check" aria-hidden="true"></i><span class="sr-only">yes</span></td>
</tr>
</tbody>
</table>
-<p>When using container technology, applications are typically run on their own and do not need to compete for memory. The OpenJ9 VM detects when it is running inside a container that imposes a memory limit, and if <code>-XX:+UserContainerSupport</code> is set, adjusts the maximum Java heap size appropriately.</p>
+<p>When using container technology, applications are typically run on their own and do not need to compete for memory. The OpenJ9 VM detects when it is running inside a container that imposes a memory limit, and adjusts the maximum Java heap size appropriately.</p>
<p>The following table shows the values that are used when <code>-XX:+UserContainerSupport</code> is set:</p>
<table>
<thead>
@@ -2908,8 +2908,9 @@
<ol>
<li>The application is running in a container environment.</li>
<li>The memory limit for the container is set.</li>
-<li>The <code>-XX:+UseContainerSupport</code> option is specified on the command line, which is expected to be the default in a future release.</li>
+<li>The <code>-XX:+UseContainerSupport</code> option is set, which is the default behavior.</li>
</ol>
+<p>To prevent the VM adjusting the maximum heap size when running in a container, set <code>-XX:-UseContainerSupport</code>.</p>
<p>When <a href="../xxmaxrampercentage/"><code>-XX:MaxRAMPercentage</code></a> or <a href="../xxinitialrampercentage/"><code>-XX:InitialRAMPercentage</code></a> are used with <code>-XX:+UseContainerSupport</code>, the corresponding heap setting is determined based on the memory limit of the container. For example, to set the maximum heap size to 80% of the container memory, specify the following options:</p>
<div class="codehilite"><pre><span></span>-XX:+UseContainerSupport -XX:MaxRAMPercentage=80
</pre></div>
