Increase the memory allocated to the DPA Java heap

With the default maximum Java heap setting, DPA can monitor up to 20 database instances. Increase this value to monitor additional database instances.

Task 1: Determine the appropriate Java heap size

Determine the appropriate Java heap size for a DPA server based on the number of instances that server monitors.

Number of monitored instances	Amount of memory to allocate
1-20	4096 MB (4 GB)
21-50	8,192 MB (8 GB)
51-100	16,384 MB (16 GB)
101-250	32,768 MB (32 GB)

These estimates are based on testing done with an average of two or three active sessions per monitored instance. If you are monitoring busy instances with more active sessions, adjust accordingly.

Task 2: Increase the maximum heap size

Increase the size when DPA is running as a Windows service

Open the following file in a text editor:

DPAInstallDir\iwc\tomcat\ignite_config\idc\server.properties
Update the value of the maximum heap setting:

windows.service.java.heap.max.size=

Enter the value in megabytes, but without an indicator of the unit. For example, enter 8192 to increase the maximum heap size to 4 GB.
Run the following batch files to recreate the Ignite PI Server service.

SolarWinds recommends that you open the command prompt as an admin, change to the directory that includes the batch files, and then execute them. If you just click on a .bat file to execute it, the file might not run because of user access control settings, or it might appear to run but won't change the memory setting.

C:\Program Files\SolarWinds\DPA\removeWindowsService.bat C:\Program Files\SolarWinds\DPA\createWindowsService.bat

Increase the size when DPA is running from a command line on a Linux server

Open the following file in a text editor:

DPAInstallDir/iwc/tomcat/ignite_config/idc/server.properties
Update the value of the maximum heap setting:

java.max.heap.size=

Enter the value in megabytes followed by m. For example, enter 8192m to increase the maximum heap size to 4 GB.

On Linux, leaving the m out can prevent DPA from restarting.
Restart DPA.

Task 3: Verify the change

Verify the change by running a .bat file (Windows only)

Run either of the following commands in a command prompt to display the current maximum heap size:

RemoveWindowsService.bat
CreateWindowsService.bat

Verify the change in a log file (Windows and Linux)

Open the following file in a text editor:

DPAInstallDir\iwc\tomcat\logs\diagnostics\diagnosticSystem.json

In the "inputArguments" section, search for the -Xmx setting and verify the value.

"runtimeBean" : {
    "vmName" : "OpenJDK 64-Bit Server VM",
    "vmVendor" : "Oracle Corporation",
    "vmVersion" : "14+36-1461",
    "uptime" : "4d 16h 54m 53s",
    "specName" : "Java Virtual Machine Specification",
    "specVendor" : "Oracle Corporation",
    "inputArguments" : [ "-Dcatalina.home=C:\\Program Files\\SolarWinds\\DPA\\iwc\\tomcat", "-Dcatalina.base=C:\\Program Files\\SolarWinds\\DPA\\iwc\\tomcat", "-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", "abort", "-Xms256m", "-Xmx4096m", "-Xss256k" ],

Search SolarWinds Support