Help
NetFlow Analyzer is a resource-intensive product and needs to be tuned for best performance based on available system resources. It comes with default tuning for 2 GB. If installed on a dedicated machine with plenty of RAM and CPU, tuning can improve performance. Click here to refer to the flow rate based system requirement for NetFlow Analyzer. To tune the product, first check the database by clicking the Profile Icon on the top right corner and navigating to Installation Info. If using MSSQL, tune Java component alone. Steps for tuning Java and Postgres database for better performance are as follows.
Java Tuning
1. Shutdown OpManager service.
2. Open the file "wrapper.conf" present under the OpManager_Home/conf/ directory in a text editor. Find the following line in the file
Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=8192
Postgres database Tuning
For 12.7.x, customer specific PostgreSQL tuning parameters should be added in OpManager/pgsql/ext_conf/customer_ext.conf
shared_buffers=512MB
work_mem=80MB
maintenance_work_mem=1900MB
effective_cache_size=5120MB
Java Tuning
1. Shutdown OpManager service.
2. Open the file "wrapper.conf" present under the OpManager_Home/conf/ directory in a text editor. Find the following line in the file
Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=6144
Postgres database Tuning
For 12.7.x, customer specific PostgreSQL tuning parameters should be added in OpManager/pgsql/ext_conf/customer_ext.conf
shared_buffers=512MB
work_mem=20MB
maintenance_work_mem=1024MB
effective_cache_size=2560MB
Java Tuning
1. Shutdown OpManager service.
2. Open the file "wrapper.conf" present under the OpManager_Home/conf/ directory in a text editor. Find the following line in the file
Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=2048
Postgres database Tuning
For 12.7.x, customer specific PostgreSQL tuning parameters should be added in OpManager/pgsql/ext_conf/customer_ext.conf
shared_buffers=512MB
work_mem=10MB
maintenance_work_mem=1024MB
effective_cache_size=1280MB
Java Tuning
1. Shutdown OpManager service.
2. Open the file "wrapper.conf" present under the OpManager_Home/conf/ directory in a text editor. Find the following line in the file
Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=8192
Postgres database Tuning
For 12.5x and 12.6x, customer specific PostgreSQL tuning parameters should be added in OpManager/pgsql/ext_conf/zz_itom_ext.conf
shared_buffers=512MB
work_mem=80MB
maintenance_work_mem=1900MB
effective_cache_size=5120MB
Java Tuning
1. Shutdown OpManager service.
2. Open the file "wrapper.conf" present under the OpManager_Home/conf/ directory in a text editor. Find the following line in the file
Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=6144
Postgres database Tuning
For 12.5x and 12.6x, customer specific PostgreSQL tuning parameters should be added in OpManager/pgsql/ext_conf/zz_itom_ext.conf
shared_buffers=512MB
work_mem=20MB
maintenance_work_mem=1024MB
effective_cache_size=2560MB
Java Tuning
1. Shutdown OpManager service.
2. Open the file "wrapper.conf" present under the OpManager_Home/conf/ directory in a text editor. Find the following line in the file
Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=2048
Postgres database Tuning
For 12.5x and 12.6x, customer specific PostgreSQL tuning parameters should be added in OpManager/pgsql/ext_conf/zz_itom_ext.conf
shared_buffers=512MB
work_mem=10MB
maintenance_work_mem=1024MB
effective_cache_size=1280MB
Follow these steps in case your 32 Bit machine is running with RAM of 3 GB or more.
1. Shutdown OpManager service.
2. Open the file "wrapper.conf" present under the OpManager_Home/conf/ directory in a text editor. Find the following line in the file
# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=256
Change the value of "wrapper.java.maxmemory" from 256 to 1024.
The modified line will look like the following.
# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=1024
Save the wrapper.conf file.
64 Bit machine running 8 GB of RAM or More
# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=4096
64 Bit machine running 16 GB of RAM or More
# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=8192
3. Open the file "run.bat/sh" present under the OpManager_Home/bin/ directory in a text editor. Find the following lines in the run.bat file
64 Bit Machine with 8 GB of RAM or more
Change "-Xmx512m" to -Xmx4096m.
64 Bit Machine with 16 GB of RAM or more
Change "-Xmx512m" to -Xmx8192m.
Save the run.bat/sh file
4. Start OpManager service.
The above mentioned steps helps you tune the Java of NetFlow Analyzer installed on Windows and Linux machines. Now, the database tuning steps.
Windows and Linux
1. Stop the OpManager service.
2. Navigate to <OpManager\pgsql\data> folder, open the file "postgres_ext.conf", if you are not able to find this file, open a fresh file in the editor and update the values as mentioned below and save the file as "postgres_ext.conf".
64 Bit Machine Postgres Tuning
For a 64 machine running with 8 GB of RAM or more,
#$Id$
port = 13310
shared_buffers = 512MB
work_mem = 10MB
maintenance_work_mem = 600MB
checkpoint_segments = 15
checkpoint_timeout = 11min
checkpoint_completion_target = 0.9
seq_page_cost = 1.0
random_page_cost = 2.0
effective_cache_size = 3072MB
synchronous_commit=off
For a 64 machine running with 16 GB of RAM or more,
#$Id$
port = 13310
shared_buffers = 512MB
work_mem = 20MB
maintenance_work_mem = 800MB
checkpoint_segments = 15
checkpoint_timeout = 11min
checkpoint_completion_target = 0.9
seq_page_cost = 1.0
random_page_cost = 2.0
effective_cache_size = 8192MB
synchronous_commit=off
3. Start the OpManager service.
Note:
1. In case you are running with 1024 MB of RAM or less and experiencing slow response, you may want to try upgrading the RAM.
2. For MSSQL database, database tuning is not needed, you can tune just Java.
If you have any questions, send a mail to netflowanalyzer-support@manageengine.com.