F Tuning 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

See the Oracle WebLogic Server documentation for more information about setting parameters for items such as execute queues, connection pools, and timeouts.

For the MSLVPool, set the Maximum Capacity = Threads Maximum

1. Log in to the WebLogic Server Administration Console.

2. In the Domain Structure tree, expand Services, and then click Data Sources.

   The Summary of JDBC Data Sources page appears.

3. Select mslvDataSource.

   The Settings for mslvDataSource page appears.

4. Select the Configuration tab.

5. Select the Connection Pool tab.

6. Set the Maximum Capacity field to 100.

7. Click Save.

8. Under the Change Center pane, click Activate Changes.

This section describes how to setup the JVM memory argument settings. The MSS startup scripts are located under the MSLV_Home/domain directory where MSLV_Home is the path of your MSS domain. The following lists the startup script files with the first script in the list used for single servers and the remaining scripts used for clustered servers:

For Windows Operating Systems

• startMSLVSingle.cmd

• startMSLVManaged.cmd

• startAdminServer.cmd

• startProxyServer.cmd

For Windows Operating Systems

• startMSLVSingle.sh

• startMSLVManaged.sh

• startAdminServer.sh

• startProxyServer.sh

The following is an example of the settings which can be configured. (The parameters are separated onto separate lines for readability.)

set MEM_ARGS=
-Xms8g 
-Xmx8g 
-XX:NewRatio=4 
-XX:SurvivorRatio=4 
-XX:TargetSurvivorRatio=80 
-XX:MaxMetaspaceSize=386m

You can configure the following parameters:

• Xms: This option sets the initial and minimum Java heap size. The Java heap is the memory portion where blocks of memory are allocated to objects and freed during garbage collection. The MSS default value for 64-bit operating systems is “1g" for Windows and “8g" for all other platforms.

• Xmx: This option sets the maximum Java heap size. The optimum value varies based on your operating system. The MSS default value for 64-bit operating systems is “4g" for Windows and “8g" for all other platforms.

• NewRatio: This option sets the ratio between young and tenure or old generation. This sets the young generation size in relation to the size of the old generation. The young generation contains the pool of objects that have survived garbage collection of the Eden space. The tenure generation contains the pool of objects that exist in the survivor space. The MSS default value is “4." With this setting, the old generation will be four times as large as the young generation.

• SurvivorRatio: This option specifies how large of a size the Eden space is relative to one of the two survivor spaces. This value sets the ratio of Eden size to one survivor space size. The MSS default value is “4."

• TargetSurvivorRatio: This option specifies the target percentage and the allowable fullness of the survivor space. The MSS default value is “80" or 80%. This setting allows more memory to be utilized and aids high throughput applications.

• MaxMetaspaceSize: This option allows you to limit the amount of native memory used for class metadata. Without a setting, the Metaspace will dynamically re-size depending of the application demand at runtime. With this Java version, class metadata is stored in the native heap and this space is called Metaspace. By default class metadata allocation is only limited by the amount of available native memory. The MSS default value is “386m."

There are no standard memory argument settings for the JVM. The MSS default values are suggestions and can be changed to optimally tune your JVM, given your current configuration (operation system and the number of CPUs for example). At a minimum, set the initial heap size (Xms) and maximum heap size (Xmx) to equal values. The startup time can be slightly longer, but for long-running applications it provides an overall better performance. Please review your operating system and set the best possible memory argument values for your configuration. See the Oracle WebLogic Server documentation for more information.