|Maintenance Notice - PDF Generation|
|Dynamic PDF generation for web-based content is temporarily unavailable. This maintenance affects dynamic PDF files that are generated from either the HTML-based page or manual that you are viewing. Links that normally allow this functionality have been hidden, and will reappear as soon as the feature is restored.
Performance Tuning with Java Virtual Machine
Use the following parameter settings in Java Virtual Machine (JVM) Garbage Collection (GC) to maximize the performance of GRE and GRAT.
-server -Xms2G -Xmx2G -XX:+UseG1GC -XX:MaxGCPauseMillis=200 -XX:ParallelGCThreads=5 -XX:ConcGCThreads=5 -XX:InitiatingHeapOccupancyPercent=10
Highly Recommended For GC log
These settings help in debugging JVM performance problems.
-XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=20M -Xloggc:[path to gc log file]
Highly Recommended for Out Of Memory Heap Dump
-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=[path to heap dump file]
- For most cases 2G for -Xms (heap space min) and -Xmx (heap space max), as in the above required settings, will suffice. In some marginal cases, you may need to increase or decrease the heap space.
- If GRE has a lot of rules deployed, then the Xms/Xmx values must be increased to leave enough heap space to execute the requests at the required rate.
- If rule packages alone consume about 3G of heap when loaded in memory, you should use approximately 6G as the value for Xms and Xmx.
- If there are only few rule packages (each with only few rules) then 1GB of heap space should be enough.