IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Performance tuning > Tivoli Enterprise Portal client
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Tuning the portal client JVM
The memory usage of the portal client JVM increases as the size of the monitoring environment increases. If the maximum Java heap size setting is too low, the JVM spends a significant amount of time performing garbage collection. This can result in poor portal client response time and high CPU utilization.
The default value for the maximum Java heap size differs by client type, as shown in Table 1.
Default Java heap size parameters by portal client type
Client type Initial Java heap size (-Xms) Maximum Java heap size (-Xmx) Where specified Browser 128 MB 512 MB For portal server on Windows: <itm_install_dir>\cnb\ jreconfig.js
For portal server on xLinux, zLinux, or AIX:
<itm_install_dir>/ <arch>/cw/jreconfig.js
Desktop 128 MB 256 MB for 32-bit OS environments 512 MB for 64-bit OS environments
- cnp.bat (Windows)
- cnp.sh (Linux)
- in install_dir/CNP
Java Web Start Desktop client 128 MB 512 MB <itm_install_dir>\Config\tep.jnlpt After modification of this file, you will need to run a re-configuration of the portal server in order for the associated Java Web Start deployment files to be regenerated.
Parent topic:
Tivoli Enterprise Portal client