Specifying JVM Heap Size

The default Java heap size, which varies according to platform, is a conservative estimate made by the developers of the particular type of Java being used.

When you calculate the amount of memory required for an AppNode, you should determine the largest heap size that can reside in a physical memory. For best engine performance, paging to disk should be avoided.

The recommended heap size for a small workload is 1024 MB, for medium 2048MB, and for large workload 4GB or more. The recommendations change based on the scenarios, payload and workload.

To set the JVM available memory, use the following parameters:
  • The Initial JVM Size parameter sets the minimum amount of memory used.
  • The maximum JVM Size sets the maximum amount of memory used.

    For more information, see Setting Appnode JVM Parameters .

Note: It is recommended to set the minimum and maximum JVM size to same value.

The total amount of JVM memory required to operate a TIBCO BusinessWorks™ Container Edition engine should be the memory for each process plus the maximum number of processes that can be in the process pool. If flow control is enabled, the process pool can contain up to the Max Jobs value.

Note: While uploading ears, deploying applications, and browsing, increase the heap size in bwagent and AppSpace.tra files. The property specified in the AppSpace.tra file applies to all AppNodes associated with the AppSpace. However, the property specified in the AppNode.tra file only applies to a specific AppNode and overwrites the property specified in the AppSpace.tra file. The property specified in bwagent.tra does not overwrite properties in the AppNode.tra or the AppSpace.tra files.