Submit a ticketCall us

Welcome to the NEW Success Center. Search all resources (documentation, videos, training, knowledge base articles) or browse resources by product. If you are unable to find what you are looking for, please contact us at customersuccess@solarwinds.com

 

 

 

 

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

Increase DPA heap memory to monitor large numbers of instances

Overview

This article describes how to increase the amount of heap memory that is allocated to DPA to allow monitoring of large numbers of instances.

The default memory settings in DPA are:

  • DPA 9.1 and later (64-bit): Minimum of 256 MB, but can increase to 1024 MB.
  • DPA 9.1 and later (32-bit): Minimum of 256 MB, but can increase to 512 MB.
  • DPA 9.0 and earlier: Minimum of 128 MB, but can increase to 512 MB. 

Environment

DPA and Ignite 7.0 and later

Steps

DPA or Ignite running as a Windows service

 
  1. Edit the <installDir>\iwc\tomcat\ignite_config\idc\server.properties file.
  2. Update the maximum heap setting:
    1. All versions of DPA and Ignite 8.2 and later: Update the maximum heap setting (the default is 512 MB): windows.service.java.heap.max.size=
      For 32-bit and 64-bit JREs, the value is specified in decimal without the units. For example:
      1. Set it to 1024 to increase the maximum to 1 GB. This is safe for 32-bit JREs.
      2. Set it to 2048 to increase the maximum to 2 GB. Only go above 1228 with 64-bit JREs.
    2. Ignite 8.1 and earlier: Update the maximum heap setting. The default is 0x0200, which is hexadecimal and means 512 MB): windows.service.java.max.heap.size.in.hex=
      1. For 32-bit JREs (the default), the value is specified in hexadecimal.  For example:
        1. Set it to 0x300 to increase the maximum to 756 MB. 
        2. Set it to 0x400 to increase the maximum to 1 GB.
      2. For 64-bit JREs, the value is specified in decimal without the units. This may seem odd given that the property name says in.hex, but a decimal value is needed. For example:
        1. Set it to 1024 to increase the maximum to 1 GB.
        2. 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 or Ignite running from a command line (UNIX, Linux or Windows)

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

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.  Typically, the highest setting on Windows with a 32-bit JRE is 1536 MB (=0x600), and on Solaris is 3.8 GB (=0xED8).

For more information on this issue, you can read an article from Oracle.

If the Max Java Heap Size is set too high, DPA or Ignite will not start.  The Max Heap setting should be lowered.

If you need a higher Max Java Heap Size setting than the operating system allows, there are several solutions:

  • Add memory to your server. For 32-bit Windows, this may not help since 32-bit Windows has limitations on addressable memory.
  • If you are using 32-bit Windows to host DPA or Ignite, you can change operating systems to:
    • UNIX
    • Linux
    • 64-bit Windows with a 64-bit JRE. See this KB article for more information.
  • If none of the above is possible, set the Max Java Heap Size as high as you can. If that is enough to monitor, and you are running any version of DPA or Ignite 7.0 or later, you can disable the message saying that Configuration settings are insufficient to monitor X database instances by performing the following: 
    1. Edit the <installDir>\iwc\tomcat\ignite_config\idc\system.properties file.
    2. Set the following property:

      com.confio.idc.heap.size.check.enable = false

    3. Restart DPA or Ignite.

      DPA or Ignite will still warn you if heap space is getting full.

Last modified
19:14, 22 Jun 2016

Tags

Classifications

Public