This appendix provides recommended configurations to tune your servers for performance.
The configuration information given in this document is for a baseline setup.To achieve optimum performance for individual business needs, load and performance testing in a test environment that represents your true production environment is required. The test environment should mimic how you use your production system, including the transaction mix, number of users, hardware and software infrastructures, database, network usage, and all other relevant factors. Setting up a test environment will allow you to determine the settings that you should have for your production environment for:
Connection pool sizing
Java memory management
For information on setting parameters for execute queues, connection pools, timeouts, and so on, see the following Web site:
http://docs.oracle.com/cd/E12840_01/wls/docs103/sitemap.html
For the MSLVPool, set the Maximum Capacity = Threads Maximum
From the WebLogic Server Administration Console, select Services.
Select JDBC.
Select Data Sources.
Select mslvDataSource.
Select the Configuration tab.
Select the Connection Pool tab.
Set the Maximum Capacity field to 100.
Click Save.
Under the Change Center pane, click Activate Changes.
In the MSS 6.2.x startup script under the MSLV_Home/domain directory, the following settings can be configured:
MEM_INIT=1024m MEM_MAX=1024m PERMSIZE=192m (for non-XML) and 256m (for XML) MAXPERMSIZE= 384m (for non-XML) and 512m (for XML) Set the MEM_INT value equal to the MEM_MAX value.
Note that in a Windows environment, JVM cannot take advantage of memory more than 1.2 GB. the value of (MEM_MAX + MAXPERMSIZE). The memory needs to be in a continuous block.
For other operating systems, the JVM limitation is 4GB in a continuous memory block. In some cases to date, a system had 2GB free memory but the java process was not able to start. This is because the machine was up for some time and due to the memory fragmentation, JVM was not able to obtain a continuous memory block of 2GB. The only way to resolve this is to reboot the server machine. Then, immediately restart the application server.