...
The Peer Server load is the number of components which are launched by it. Components can be launched in-memory - which means the component runs in the same VM as the Peer Server. For each component, a set of JMS resources are created which consume Heap Memory and a certain number of threads are created per JMS session spawned. For components launched in-memory, the classes loaded for the components to be launched affect the VM perm gen space as well as the memory required by the component to run.
| Anchor |
|---|
...
|
...
|
The following tree gives you a guideline of the JVM hotspot settings for a set of combinations for the above factors. These recommendations are only guidelines and not stead-fast rules. It is recommended to tune the server starting with one of the recommended settings which match closely with the setup. These recommendations have consistent system behavior as their top priority, followed by performance.
These recommendations do not incorporate the dimension associated with processing messages of a certain size. These recommendations assume that the message sizes are below 1 MB and will not actually affect the memory required by the Peer Server to process the messages.
| Note |
|---|
The JVM hotspot setting is recommended below especially for those which starts with '-XX' keyword, are non-standard hotspot options and are not guaranteed to be supported by all JAVA VM implementations. For example, IBM JRE does not support many of the these options. The recommendations below have been made assuming that Sun JRE is being used to run the servers. In case some other JAVA VM is used, users are advised to find out corresponding options as provided by VM vendor. |
...