Change the size of the JVM heap

Here’s how to change the the size of the heap in your DataSource application’s Java Virtual Machine (JVM) from the default settings. You might need to do this for performance reasons.

Change the heap size using the jvm-options configuration item:

jvm-options    -Xms$<min-heap-size>m -Xmx$<max-heap-size>m

-Xms<min-heap-size>m specifies the initial size of the heap, in megabytes.

-Xmx<max-heap-size>m specifies the maximum size of the heap, in megabytes

We recommend that you set the <min-heap-size> and <max-heap-size> to the same value.

For more about the Java -Xms and -Xmx command line options, see the Java documentation about the java command.

Where do I put the configuration?

What I’m developing/customising configuration GOES IN

Adapter: Developing an existing Java-based Adapter blade.

Blade’s DataSource/etc/java.conf

Adapter: Customising an existing Java-based Adapter blade.

Deployment Framework’s global_config/overrides/<blade-name>/DataSource/java.conf

Liberator: Developing a Java-based Liberator Permissioning Service blade.

Blade’s Liberator/etc/java.conf

Liberator: Customising a Java-based Liberator Permissioning Service blade.

Deployment Framework’s global_config/overrides/<blade-name>/Liberator/etc/java.conf

Liberator: Applying heap configuration to all Java modules in Liberator (including JMX), except when specifically overridden by particular blades.

Deployment Framework’s global_config/overrides/servers/Liberator/etc/java.conf

Transformer: Developing a Java-based Transformer Service blade.

Blade’s Transformer/etc/java.conf

Transformer: Customising an existing Java-based Transformer Service blade.

Deployment Framework’s global_config/overrides/<blade-name>/Transformer/etc/java.conf

Transformer: Applying heap configuration to all Java modules in Transformer (including JMX), except when specifically overridden by particular blades.

Deployment Framework’s global_config/overrides/servers/Transformer/etc/java.conf


See also: