Siebel on Sun Solaris: More Performance with Less mprotect() Calls

By default each transaction in Siebel CRM application makes a large number of serialized mprotect() calls, which in turn may degrade the performance of Siebel. When the load is very high on Siebel enterprise servers, the mprotect() calls are serialized by the operating system kernel resulting in high number of context switches and low CPU utilization.

If the application exhibits these pathological conditions, performance thus scalability of the application can be improved by reducing the number of mprotect() during run-time with the help of AOM tunable MemProtection=FALSE.

From the command line version of Siebel Server Manager, run:
change param MemProtection=False for comp <component_alias_name> server <siebel_server_name>

where:
component_alias_name is the alias name of the AOM component to be configured, such as SCCObjMgr_enu for the Call Center Object Manager; and

siebel_server_name is the name of the Siebel Server for which the component being configured.

The MemProtection parameter is hidden; and the value of this parameter is TRUE by default.

For more information about this tunable on Solaris platform, check Siebel Performance Tuning Guide Version 7.7 or 8.0 in Siebel Bookshelf.

Related posts:

• Siebel on Sun Solaris: Know the process resource limits
  
• Solaris 9 or later: More performance with Large Pages (MPSS)
  
• Running Enterprise applications on Solaris 10

_________________
Technorati Tags:
siebel | CRM | Oracle | Sun | Solaris