Bookshelf Home | Contents | Index | Search | PDF

Performance Tuning Guide > Tuning the Siebel Application Object Manager for Performance > Best Practices for AOM Tuning >

Tuning AOM Caches

---

The AOM uses several caches, which affect memory usage for the AOM. Tuning AOM caches affects AOM performance and memory usage. The following are some of the major caches used by AOM that can be configured:

• SQL cursor cache. The SQL cursor cache is configured using the DSMaxCachedCursors parameter. This can be enabled on multithreaded components (such as AOM) with database connection pooling. The value represents the number of SQL cursors per database connection.

  For an AOM for which the Siebel Server machine is more likely to reach its CPU capacity before it reaches its memory capacity (for example, Siebel Employee Relationship Management), the default value of 16 for the DSMaxCachedCursors parameter may be appropriate. Such an application is sometimes referred to as CPU-bound.

  For an AOM for which the Siebel Server machine is more likely to reach its memory capacity before it reaches its CPU capacity (for example, Siebel Call Center), you can set DSMaxCachedCursors to a lower value, even to 0. Such an application is sometimes referred to as memory-bound.

  In general, the value should reflect the CPU and memory resource availability on the Siebel Server machine running a particular AOM component.

  The trade-off in setting this parameter is that allocating memory to caching SQL cursors means they would need to be created less often, but at a cost in memory.

• SQL data caches. The SQL data caches are configured using the DSMaxCachedDataSets parameter. Two types of data caches are guided by this parameter: global data cache, which is useful in most cases, and per-connection data cache (enabled with or without database connection pooling).

  For an AOM for which the Siebel Server machine is more likely to reach its CPU capacity before it reaches its memory capacity (for example, Siebel Employee Relationship Management), the default value of 16 for the DSMaxCachedDataSets parameter may be appropriate.

  For an AOM for which the Siebel Server machine is more likely to reach its memory capacity before it reaches its CPU capacity (for example, Siebel Call Center), you can set DSMaxCachedDataSets to a lower value, even to 0.

  In general, the value should reflect the CPU and memory resource availability on the Siebel Server machine running a particular AOM component.

  The trade-off in setting this parameter is that allocating memory to caching SQL data sets means they would need to be created less often, but at a cost in memory.

Bookshelf Home | Contents | Index | Search | PDF