Repository: nifi
Updated Branches:
  refs/heads/master 02d38b55b -> 2589df80a


NIFI-3304 removed unneeded Java 8 codecache info from Admin Guide

This closes #1621

Signed-off-by: Andre F de Miranda <[email protected]>


Project: http://git-wip-us.apache.org/repos/asf/nifi/repo
Commit: http://git-wip-us.apache.org/repos/asf/nifi/commit/2589df80
Tree: http://git-wip-us.apache.org/repos/asf/nifi/tree/2589df80
Diff: http://git-wip-us.apache.org/repos/asf/nifi/diff/2589df80

Branch: refs/heads/master
Commit: 2589df80ab1eb70327c6ed836f269967caee35fe
Parents: 02d38b5
Author: Mike Moser <[email protected]>
Authored: Fri Mar 24 21:44:07 2017 +0000
Committer: Andre F de Miranda <[email protected]>
Committed: Tue Apr 11 02:05:20 2017 +1000

----------------------------------------------------------------------
 nifi-docs/src/main/asciidoc/administration-guide.adoc | 11 -----------
 1 file changed, 11 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/nifi/blob/2589df80/nifi-docs/src/main/asciidoc/administration-guide.adoc
----------------------------------------------------------------------
diff --git a/nifi-docs/src/main/asciidoc/administration-guide.adoc 
b/nifi-docs/src/main/asciidoc/administration-guide.adoc
index d3abd3a..2de8387 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
 ---------------------

Reply via email to