From 2589df80ab1eb70327c6ed836f269967caee35fe Mon Sep 17 00:00:00 2001 From: Mike Moser Date: Fri, 24 Mar 2017 21:44:07 +0000 Subject: [PATCH] NIFI-3304 removed unneeded Java 8 codecache info from Admin Guide This closes #1621 Signed-off-by: Andre F de Miranda --- nifi-docs/src/main/asciidoc/administration-guide.adoc | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/nifi-docs/src/main/asciidoc/administration-guide.adoc b/nifi-docs/src/main/asciidoc/administration-guide.adoc index d3abd3a3ff..2de8387b2a 100644 --- a/nifi-docs/src/main/asciidoc/administration-guide.adoc +++ b/nifi-docs/src/main/asciidoc/administration-guide.adoc @@ -1777,17 +1777,6 @@ take effect only after NiFi has been stopped and restarted. configured recipients if the bootstrap determines that NiFi has unexpectedly died. |==== -*Java 8 handling of codecache* -It has been observed in Java 8 runtime environments that performance can suddenly drop by more than an order of magnitude after days or weeks of otherwise ideal -behavior. This has only been observed under extremely high load and in cases where considerable Just in Time (JIT) compilation occurs. The core problem is the CodeCache becomes -full and is seemingly not properly garbage collected or grown. When this occurs JIT seems to no longer occur or involve considerable delays and performance drops. -This is easily overcome by ensuring the following lines are available in the _boostrap.conf_. By default they are there but commented. Uncomment them for maximum sustained throughput. -.... -#java.arg.7=-XX:ReservedCodeCacheSize=256m -#java.arg.8=-XX:CodeCacheFlushingMinimumFreeSpace=10m -#java.arg.9=-XX:+UseCodeCacheFlushing -.... - [[notification_services]] Notification Services ---------------------