Modifying the JVM heap size
The Java™ virtual machine (JVM) heap size setting directly relates to how many server instances can be started within a dynamic cluster on a specific node. You might need to modify the JVM heap size setting based on your environment configuration. The default value is 256 MB. Modifying the heap size can affect application placement and the health management function.
Before you begin
About this task
total_RAM / 2 / number_of_servers = maximum_heap_size
1.5 GB / 2 = 750 MB 750 MB / 3 = 250 MBThe 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 you specified.
Procedure
- In the administrative console click .
-
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. The default maximum heap size value is 256 MB.
- Click OK.
Results
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 heap size value in the <os>.systemlaunch.properties file.