System Scaling

To properly scale your system to meet loads for the maximum number of concurrent users, you need to set the MX_CONNECTION_POOL_SIZE correctly, as well as your Oracle Sessions.

The default value setting depends on the Java Heap size entered during installation.

See Also
JVM Options
mxAudit.log File
Evaluation Details

You should monitor the 3DSpace instance in the database under typical production usage levels over a period of time and observe the number of sessions opened. This will provide a good indication of the value to use for your MX_CONNECTION_POOL_SIZE.

If more connections are required, you could increase this value by 10 or more to the value that works for your implementation under typical production usage levels.

You may also need to increase the MX_CONNECTION_POOL_SIZE value if numerous errors like the following are thrown:

Error #4000045 Creating new database connection, pool size
insufficient

This message is generated when the server needs to open a new connection. If this happens on a regular basis, the current MX_CONNECTION_POOL_SIZE value is too low.

Additionally, you should consider the Java heap sizes. -Xms (minimum heap size) should be at least 768m for large systems. -Xmx (maximum heap size) is platform-dependent, but should never exceed 1.5g.

Note: When determining the Java heap size, you need to consider that a similar amount of memory is also needed by the 3DSpace C++ kernel, which runs in the same process as the JVM but in a separate memory space and is not controlled by the Java heap size setting.