title: optimize nifi performance by changing heap size < 32 gb and leverage oops compression
body: <p>Can i tweak bootstrap.conf to start nifi with heap size &lt;32GB so that <a href="https://wiki.openjdk.java.net/display/HotSpot/CompressedOops" rel="nofollow noreferrer">oops compression</a> happens automatically. We are currently at :</p>
  
  <p><code>​java -Xmx32768m -XX:+PrintFlagsFinal 2&gt; /dev/null | grep UseCompressedOops</code> -- returns false</p>
  
  <p>From bootstrap.conf:</p>
  
  <pre><code>   java.arg.3=-Xmx32768m
  </code></pre>
  
  <p>And our heap utilization is :</p>
  
  <pre><code>"heapUtilization":"86%"
  </code></pre>
  
  <p>​Can Nifi performance improve if we leverage oops compression ? What other parameters should i monitor and improve upon ? </p>
  
  <p>EDIT 1: Also, using large heap sizes can delay the GC and hence the dataflows. Is there a optimized heapsize that everyone is already using on production ?</p>