Performance Tuning Guide > Tuning Operating Systems for Performance >
Tuning the Siebel Server for All UNIX Platforms
For all Siebel Server machines running on supported UNIX platforms, setting the environment variables described in this section can help you manage your server resources appropriately and stay within appropriate CPU-usage limits.
Environment Variable for Siebel Assert Creation
For Siebel Server machines or Web server machines, the environment variable
SIEBEL_ASSERT_MODE determines whether assert files are created. With the default setting of
0, the creation of assert files is disabled, which conserves disk space and improves performance.
This variable should be set to a non-zero value only if you are performing system diagnostics, and it should only be set in consultation with Siebel Technical Services.
For more information about this variable, see System Monitoring and Diagnostics Guide for Siebel Business Applications.
Environment Variable for Operating System Resource Limits
Set the environment variable
SIEBEL_OSD_MAXLIMITS using one of the following methods (define the variable in the applicable profile for the Siebel Server):
Setting this variable to
1 specifies that operating system maximum values for resources will apply. Such resources may include coredumpsize, cputime, filesize, descriptors, maxmemory, and others.
Environment Variable for Operating System Latches
If the total number of tasks on the Siebel Server is greater than 500, you should set the environment variables described here in order to manage these loads.
SIEBEL_OSD_NLATCH controls named latches and
SIEBEL_OSD_LATCH controls unnamed latches. Latches, which are similar to mutexes (mutual exclusion objects), are used for communication between processes.
SIEBEL_OSD_LATCH are not defined, the values are 5000 and 1000, respectively. If these values are sufficient or the total number of tasks on the Siebel Server is less than 500, you do not need to set these variables.
NOTE: Before changing these variables, stop the Siebel Server using the
stop_server command, then run the
cleansync utility. For more information about this utility, see Siebel SupportWeb.
SIEBEL_OSD_LATCH on the Siebel Server machine based on the following formulas (define the variables in the applicable profile for the Siebel Server):
SIEBEL_OSD_NLATCH = 7 * (cumulative MaxTasks for all components) + 1000
SIEBEL_OSD_LATCH = 1.2 * (cumulative MaxTasks for all components)
Assume, for example, that you have enabled two multithreaded server components on the same Siebel Server: SCCObjMgr_enu and WfProcMgr. For SCCObjMgr_enu, MaxTasks = 500 and, for WfProcMgr, MaxTasks = 100. In this example, parameter values should be as follows:
SIEBEL_OSD_NLATCH = 5200 = 7 * [500 + 100] + 1000
SIEBEL_OSD_LATCH = 720 = 1.2 * [500 + 100]