Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > Increase DPA heap memory to monitor large numbers of instances

Increase DPA heap memory to monitor large numbers of instances

Updated November 16, 2017

Overview

This article describes how to increase the amount of heap memory that is allocated to DPA. Additional memory allows DPA to monitor a large number of instances.

The default memory settings in DPA are:

  • DPA 9.1 and later (64-bit): Minimum of 256 MB, but can be increased

Environment

DPA, all versions

Steps

DPA running as a Windows service

  1. Edit the <installDir>\iwc\tomcat\ignite_config\idc\server.properties file.
  2. Update the maximum heap setting (the default is 1024 MB):
    windows.service.java.heap.max.size=
    1. The value is set in Megabytes
      • Set it to 2048 to increase the maximum to 2 GB. 
  3. Recreate the Ignite PI Server service by running two batch files:
    • C:\Program Files\SolarWinds\DPA\removeWindowsService.bat
    • C:\Program Files\SolarWinds\DPA\createWindowsService.bat

DPA running from a command line (Unix, Linux)

  1. Edit the <installDir>\iwc\tomcat\ignite_config\idc\server.properties file.
  2. Update the following setting. The default is 1024m which means 1024 MB:
    java.max.heap.size=
    • Set it to 2024m to increase the maximum to 1 GB. 
  3. Restart DPA or Ignite by running two scripts:
    • Unix or Linux: shutdown.sh and startup.sh

Verifying the change

Windows service 

When running the batch files on most windows servers is works best to open a command prompt as an admin and changed directory to the path that has the batch files then execute them. Support has seen the .bat blocked by some User access control settings or it will flash on the screen and not change the memory setting when simply clicking to execute the .bat file. 

The following shows the files run in command line and a successful change to 2048 MB max memory.

RemoveWindowsService.bat Output:

removeWindowsServicebat.png

 

CreateWindowsService.bat Output:

createWindowsServicebat.png

 

Verifying the change in log files on both Windows and Linux

To verify the increase of java heap memory we can look in the system.log file located in  

<installDir>\iwc\tomcat\logs\system.log 

The java heap memory setting can be found by searching the file in a text editor for 

-Xmx 

 

Example here from a Windows install the line is as follows. 

InputArguments: -Dcatalina.home=C:\Program Files\SolarWinds\DPA\iwc\tomcat -Dcatalina.base=C:\Program Files\SolarWinds\DPA\iwc\tomcat -Djava.endorsed.dirs=C:\Program Files\SolarWinds\DPA\iwc\tomcat\endorsed -Djava.io.tmpdir=C:\Program Files\SolarWinds\DPA\iwc\tomcat\temp -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=C:\Program Files\SolarWinds\DPA\iwc\tomcat\conf\logging.properties exit -Xms256m -Xmx2048m -Xss256k

 

Warning: Max Java Heap Size can be set too high

The Max Java Heap Size setting can be set too high for your operating system. For example, Windows requires contiguous memory space. Since Windows loads DLLs that can easily fragment memory, higher Max Java Heap Size settings can be difficult to attain. 

 

Often where this is a problem is if DPA is running on a VM and there is dynamic memory in use with no reservation set on the memory.

 

For example: 

DPA is running on a VM with dynamic memory set of 10 GB ram and the default java heap memory of 1024 MB of memory. The above steps are taken to scale DPA to use 6 GB memory or 6144 MB of memory however at the time of the adjustment the VM isn't using or does not have a reserve on the memory from the host. DPA may not start up. 

 

Last modified

Tags

Classifications

Public