Users Guide

Optimizing Your System | Getting Started
112 OMNM 6.5.3 User Guide
Portal Memory Settings
To manually change OpenManage Network Manager web portal heap settings, change the
setenv.sh (Linux) or setenv.bat (Windows) file:
set "PORTAL_PERMGEN=512m"
set "PORTAL_MAX_MEM=3072m"
set "PORTAL_INIT_MEM=768m"
set "PORTAL_32BIT_MAX_MEM=768m"
These files are in the Tomcat***/bin directory. After you change their settings, for Linux, restart
the portal service to apply new memory settings. In Windows, besides updating
setenv.bat you
must run
service.bat update in that same directory.
You can increase these to even higher figures if your system has the memory available.
NOTE:
Make sure only one Tomcat process is running, otherwise your web server may exhibit poor
performance.
Memory Limits Advice
RAM size on hardware can increase virtually without limit. However, if you configure application
server so it does not use half of the configured Heap, then having such a large Heap degrades
performance since Java (this software’s programming language) scans and sizes garbage collection
with the pre-allocated large Heap in mind.
That is not to say servers cannot have large amounts of memory. As the applications goes into
production and usage grows, larger RAM lets you adjust to meet demand as it grows. Having a small
amount of RAM does not allow for growth when needed.
Another thing to remember: Suppose a host has 32GB for an Application Server. Say the
Application Server Heap is 28GB. This limits the amount of Threads you can run simultaneously
in Thread Pools as well as I/O forking. Every time Java executes a thread, it allocates memory
outside of its VM for native calls Since the server only had 32GB and the operating system must
use some, very little remains for these processes.
Best practice: Lower the Heap Memory in favor or leaving some more available to the operating
system so you can take advantage of more threads if you have the CPU cycles.
Too much Heap RAM impacts only excessive garbage collection which can equate to application
pauses as garbage collection moves memory around. Application pauses degrade performance.
Tuning Application Features’ Performance Impact
Resync, Performance, and so on use different pools than backups, so limiting the size of the
backups pool would have little impact on resync since these applications does not compete for
resources.
If you need to configure these, you can configure pool sizes using properties in
installed.properties . On startup the application server creates a file called
mbean_attr_overrides.template in owareapps/installprops/lib . This includes
text descriptions of Mbeans and their settable properties. It allows you to copy properties you want
to override and add them to the existing
install.properties , so the settings persist even if
you upgrade the software. This replaces a previous tuning method that required editing
mbean-
settings.xml
and did not persist past upgrade.