Modify the JVM heap size

The JVM heap size setting directly relates to how many server instances can be started within a dynamic cluster on a specific node. We might need to modify the JVM heap size setting based on the environment configuration. odifying the heap size can affect application placement and the health management function.

Before modifying the JVM heap size, read about tuning Java virtual machines.

The total value of all server JVM heap sizes within the dynamic cluster for a specific node must be less than half of the total RAM of that computer. To determine the maximum heap size setting for a single server instance, use the following equation:

total_RAM / 2 / number_of_servers = maximum_heap_size 

For example, to support three servers on a machine with 1.5 GB of RAM:

1.5 GB / 2 = 750 MB
750 MB / 3 = 250 MB

The maximum heap size is 250 MB for each server instance.

The following table contains some maximum heap size samples.

Intelligent Management server total RAM in GB	Number of supported servers	Dynamic cluster size in MB	Approximate maximum heap size in MB
1.5	1	Less than 750	750
1.5	2	Less than 750	375
1.5	3	Less than 750	250
2	1	Less than 1000	1000
2	2	Less than 1000	500
2	3	Less than 1000	333

When a dynamic cluster creates server instances, a server template is used to set initial values for the newly created server instance. The following steps outline the procedure for modifying JVM heap size within the server template. Newly created server instances can then use the maximum heap size we specified.

Tasks

1. From the admin console, click...

           Servers > Clusters > Dynamic clusters > dynamic_cluster_name > Server template > Java and process management > Process definition > Java virtual machine.

2. Modify the heap size accordingly. Typically, the total value of all server instance JVM heap sizes on a specific node must be less than half of the total RAM of that computer.

3. Click OK.

The heap size defined in the dynamic cluster template is configured on each server in the dynamic cluster. If the server and application placement controller are on the same node, the application placement controller can retrieve the heap size from this configured value.

If the server is not on the same node as the application placement controller, the application placement controller obtains the heap size from the configuration repository in the deployment manager. If the deployment manager is not available or the heap size is not defined on the deployment manager, the application placement controller tries to obtain the heap size by contacting the server. If the server is not available, the application placement controller uses the default Maximum heap size.

Tune the JVM