Generated from commit: 7628a5cf77fc57c18ced80e157ea97b28c095e91
diff --git a/search/search_index.json b/search/search_index.json
index e6b24cb..6fad380 100644
--- a/search/search_index.json
+++ b/search/search_index.json
@@ -1217,7 +1217,7 @@
},
{
"location": "/xcodecachetotal/",
- "text": "-Xcodecachetotal\n\n\nUse this option to set the maximum size limit for the JIT code cache. This option also affects the size of the JIT data cache.\n\n\nSyntax\n\n\n -Xcodecachetotal<size>\n\n\n\n\n\nSee \nUsing -X command-line options\n for more information about specifying the \n<size>\n parameter.\n\n\nExplanation\n\n\nBy default, the total size of the JIT code cache is determined by your operating system, architecture, and the version of the VM that you are using. Long-running, complex, server-type applications can fill the JIT code cache, which can cause performance problems because not all of the important methods can be JIT-compiled. Use the \n-Xcodecachetotal\n option to increase the maximum code cache size beyond the default setting, to a setting that suits your application.\n\n\nThe value that you specify is rounded up to a multiple of the code cache block size, as specified by the \n-Xcodecache\n option. If you specify a value for the \n-Xcodecachetotal\n option that is smaller than the default setting, that value is ignored.\n\n\nWhen you use this option, the maximum size limit for the JIT data cache, which holds metadata about compiled methods, is increased proportionally to support the additional JIT compilations.\n\n\nThe maximum size limits, for both the JIT code and data caches, that are in use by the VM are shown in Javadump output. Look for lines that begin with \n1STSEGLIMIT\n. Use this information together with verbose JIT tracing to determine suitable values for this option on your system. For example Javadump output, see \nInterpreting a Java dump: Storage Management (MEMINFO)\n.\n\n\nSee also\n\n\n\n\n-Xjit\n\n\nUsing Javadump",
+ "text": "-Xcodecachetotal\n\n\nUse this option to set the maximum size limit for the JIT code cache. This option also affects the size of the JIT data cache.\n\n\nSyntax\n\n\n -Xcodecachetotal<size>\n\n\n\n\n\nThe default size is 256 MB for a 64-bit VM and 64 MB for a 31/32-bit VM.\n\n\nSee \nUsing -X command-line options\n for more information about specifying the \n<size>\n parameter.\n\n\nExplanation\n\n\nBy default, the total size of the JIT code cache is 256 MB for a 64-bit VM and 64 MB for a 31/32-bit VM. Long-running, complex, server-type applications can fill the JIT code cache, which can cause performance problems because not all of the important methods can be JIT-compiled. Use the \n-Xcodecachetotal\n option to increase or decrease the maximum code cache size to a setting that suits your application. The minimum size of the code cache is restricted to 2 MB.\n\n\nThe value that you specify is rounded up to a multiple of the code cache block size, as specified by the \n-Xcodecache\n option. If you specify a value for the \n-Xcodecachetotal\n option that is smaller than the default setting, that value is ignored.\n\n\nWhen you use this option, the maximum size limit for the JIT data cache, which holds metadata about compiled methods, is increased or decreased proportionally to support the JIT compilations.\n\n\nThe maximum size limits, for both the JIT code and data caches, that are in use by the VM are shown in Javadump output. Look for lines that begin with \n1STSEGLIMIT\n. Use this information together with verbose JIT tracing to determine suitable values for this option on your system. For example Javadump output, see \nJava dump: Storage Management (MEMINFO)\n.\n\n\nSee also\n\n\n\n\n-Xjit",
"title": "-Xcodecachetotal"
},
{
@@ -1227,17 +1227,17 @@
},
{
"location": "/xcodecachetotal/#syntax",
- "text": "-Xcodecachetotal<size> See Using -X command-line options for more information about specifying the <size> parameter.",
+ "text": "-Xcodecachetotal<size> The default size is 256 MB for a 64-bit VM and 64 MB for a 31/32-bit VM. See Using -X command-line options for more information about specifying the <size> parameter.",
"title": "Syntax"
},
{
"location": "/xcodecachetotal/#explanation",
- "text": "By default, the total size of the JIT code cache is determined by your operating system, architecture, and the version of the VM that you are using. Long-running, complex, server-type applications can fill the JIT code cache, which can cause performance problems because not all of the important methods can be JIT-compiled. Use the -Xcodecachetotal option to increase the maximum code cache size beyond the default setting, to a setting that suits your application. The value that you specify is rounded up to a multiple of the code cache block size, as specified by the -Xcodecache option. If you specify a value for the -Xcodecachetotal option that is smaller than the default setting, that value is ignored. When you use this option, the maximum size limit for the JIT data cache, which holds metadata about compiled methods, is increased proportionally to support the additional JIT compilations. The maximum size limits, for both the JIT code and data caches, that are in use by the VM are shown in Javadump output. Look for lines that begin with 1STSEGLIMIT . Use this information together with verbose JIT tracing to determine suitable values for this option on your system. For example Javadump output, see Interpreting a Java dump: Storage Management (MEMINFO) .",
+ "text": "By default, the total size of the JIT code cache is 256 MB for a 64-bit VM and 64 MB for a 31/32-bit VM. Long-running, complex, server-type applications can fill the JIT code cache, which can cause performance problems because not all of the important methods can be JIT-compiled. Use the -Xcodecachetotal option to increase or decrease the maximum code cache size to a setting that suits your application. The minimum size of the code cache is restricted to 2 MB. The value that you specify is rounded up to a multiple of the code cache block size, as specified by the -Xcodecache option. If you specify a value for the -Xcodecachetotal option that is smaller than the default setting, that value is ignored. When you use this option, the maximum size limit for the JIT data cache, which holds metadata about compiled methods, is increased or decreased proportionally to support the JIT compilations. The maximum size limits, for both the JIT code and data caches, that are in use by the VM are shown in Javadump output. Look for lines that begin with 1STSEGLIMIT . Use this information together with verbose JIT tracing to determine suitable values for this option on your system. For example Javadump output, see Java dump: Storage Management (MEMINFO) .",
"title": "Explanation"
},
{
"location": "/xcodecachetotal/#see-also",
- "text": "-Xjit Using Javadump",
+ "text": "-Xjit",
"title": "See also"
},
{
diff --git a/sitemap.xml b/sitemap.xml
index 3736011..d968f94 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -12,7 +12,7 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/introduction/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -21,25 +21,25 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/version0.11/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/version0.10/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/version0.9/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/version0.8/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -48,7 +48,7 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/gc/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -56,7 +56,7 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/jit/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -64,7 +64,7 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/aot/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -72,7 +72,7 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/shrc/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -81,25 +81,25 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/diag_overview/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/dump_javadump/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/dump_heapdump/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/dump_systemdump/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -109,19 +109,19 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/cmdline_specifying/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/cmdline_general/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/cmdline_migration/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -149,19 +149,19 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/tool_jdmpview/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/tool_traceformat/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/tool_builder/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -171,31 +171,31 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/openj9_support/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/openj9_defaults/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/openj9_directories/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/messages_intro/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://www.eclipse.org/openj9/docs/env_var/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -204,7 +204,7 @@
<url>
<loc>https://www.eclipse.org/openj9/docs/legal/</loc>
- <lastmod>2018-11-12</lastmod>
+ <lastmod>2018-11-15</lastmod>
<changefreq>daily</changefreq>
</url>
diff --git a/xcodecachetotal/index.html b/xcodecachetotal/index.html
index a24b2b7..26b2ed2 100644
--- a/xcodecachetotal/index.html
+++ b/xcodecachetotal/index.html
@@ -2958,16 +2958,16 @@
</pre></div>
+<p>The default size is 256 MB for a 64-bit VM and 64 MB for a 31/32-bit VM.</p>
<p>See <a href="../x_jvm_commands">Using -X command-line options</a> for more information about specifying the <code><size></code> parameter.</p>
<h2 id="explanation">Explanation</h2>
-<p>By default, the total size of the JIT code cache is determined by your operating system, architecture, and the version of the VM that you are using. Long-running, complex, server-type applications can fill the JIT code cache, which can cause performance problems because not all of the important methods can be JIT-compiled. Use the <code>-Xcodecachetotal</code> option to increase the maximum code cache size beyond the default setting, to a setting that suits your application.</p>
+<p>By default, the total size of the JIT code cache is 256 MB for a 64-bit VM and 64 MB for a 31/32-bit VM. Long-running, complex, server-type applications can fill the JIT code cache, which can cause performance problems because not all of the important methods can be JIT-compiled. Use the <code>-Xcodecachetotal</code> option to increase or decrease the maximum code cache size to a setting that suits your application. The minimum size of the code cache is restricted to 2 MB.</p>
<p>The value that you specify is rounded up to a multiple of the code cache block size, as specified by the <a href="../xcodecache/">-Xcodecache</a> option. If you specify a value for the <code>-Xcodecachetotal</code> option that is smaller than the default setting, that value is ignored.</p>
-<p>When you use this option, the maximum size limit for the JIT data cache, which holds metadata about compiled methods, is increased proportionally to support the additional JIT compilations.</p>
-<p>The maximum size limits, for both the JIT code and data caches, that are in use by the VM are shown in Javadump output. Look for lines that begin with <code>1STSEGLIMIT</code>. Use this information together with verbose JIT tracing to determine suitable values for this option on your system. For example Javadump output, see <a href="https://www.ibm.com/support/knowledgecenter/SSYKE2_8.0.0/com.ibm.java.vm.80.doc/docs/javadump_tags_meminfo.html">Interpreting a Java dump: Storage Management (MEMINFO)</a>.</p>
+<p>When you use this option, the maximum size limit for the JIT data cache, which holds metadata about compiled methods, is increased or decreased proportionally to support the JIT compilations.</p>
+<p>The maximum size limits, for both the JIT code and data caches, that are in use by the VM are shown in Javadump output. Look for lines that begin with <code>1STSEGLIMIT</code>. Use this information together with verbose JIT tracing to determine suitable values for this option on your system. For example Javadump output, see <a href="../dump_javadump/#meminfo">Java dump: Storage Management (MEMINFO)</a>.</p>
<h2 id="see-also">See also</h2>
<ul>
<li><a href="../xjit/">-Xjit</a></li>
-<li><a href="https://www.ibm.com/support/knowledgecenter/SSYKE2_8.0.0/com.ibm.java.vm.80.doc/docs/javadump.html">Using Javadump</a></li>
</ul>
<!-- ==== END OF TOPIC ==== xcodecachetotal.md ==== -->
