Bookshelf Home | Contents | Index | PDF |
Siebel Performance Tuning Guide > Tuning Siebel Application Object Manager > Performance Factors for Siebel Application Object Manager DeploymentsIn planning to deploy Siebel Application Object Managers, or in troubleshooting performance for existing Siebel Application Object Manager deployments, you must consider several factors that determine or influence performance. Factors that are central to the task of configuring the Siebel Application Object Manager are also called performance drivers. Performance drivers for Siebel Application Object Manager include concurrent users and average think time. Other important factors such as hardware resources will set limits on overall capacity or capacity per server. Subsequent topics provide information and guidelines to help you achieve and maintain optimal performance and scalability. These factors are critical in initially configuring your Siebel Application Object Managers, particularly when specifying values for the Siebel Application Object Manager component parameters MaxTasks, MaxMTServers, and MinMTServers, which are discussed in Tuning Siebel Application Object Manager Components for CPU and Memory Utilization. Concurrent UsersThe number of concurrent users is the total number of user sessions supported at any one time. It also includes sessions supporting anonymous browser users. For planning and tuning purposes, you must consider concurrent users (and total users) at multiple levels:
The maximum number of concurrent users per Siebel Server (assuming, for example, that a particular Siebel Server computer is dedicated to running Siebel Application Object Manager components) depends on the average think time, on your hardware resources, and on the nature of your Siebel Business Applications deployment. In terms of configuration, the maximum number of concurrent users for the Siebel Application Object Manager is limited by the value of the MaxTasks parameter. The effective maximum is also limited by the number of multithreaded processes for this Siebel Application Object Manager and by your hardware resources. Depending on the average think time and other factors, each multithreaded process (process within the Siebel Application Object Manager) typically supports a maximum of about 100 concurrent users. Configure enough multithreaded processes (using the MaxMTServers parameter) to support the maximum number of concurrent users required for your peak loads. NOTE: Some complex or specialized Object Manager components support fewer concurrent users. For example, Object Managers for Siebel eCommunications (part of Siebel Industry Applications) and Siebel Configurator typically support about 25 concurrent users. For more information about the Object Manager for Siebel Configurator (Siebel Product Configuration Object Manager), see Tuning Siebel Configurator. Think TimeThink time is the average elapsed time between operations performed by users in a Siebel application. Think time includes the time required by users to conduct customer interactions, enter data into the application, and work in other applications. The assumed think time has a direct relationship to the number of concurrent tasks that a multithreaded process can support. Determine the average think time based on the usage patterns typical of your user base. After the application has been configured, perform a clickstream analysis for your key processes, and try to capture the time between the user actions (operations) that are represented by the clicks. Also use the list statistics command in Siebel Server Manager to help you calculate average think time. Consider the average time between each operation (such as clicking New) and each overall transaction (such as performing all steps for creating a new contact). Mouse clicks do not equate to operations if they do not send a request to the Siebel application infrastructure. Calculate the overall average think time based on all of these factors. The ratio of 100 (100 tasks per process), based on a 30-second think time, is assumed in the formula for setting the MaxMTServers parameter. This formula is presented in Tuning Siebel Application Object Manager Components for CPU and Memory Utilization. The ratio of 100 is based on having approximately three users running operations at the exact same time (100 divided by 30 = approximately 3.3). It is generally observed that each multithreaded process can handle about three operations at the same time with minimal performance degradation. With longer think times, one multithreaded process can support more than 100 concurrent tasks; with shorter think times, fewer tasks. For example, if the think time is 15 seconds between user operations, then about 50 tasks per process could be supported (15 times 3.3 = approximately 50, or 50 divided by 15 = approximately 3.3). Nature of Siebel Application DeploymentWhich Siebel applications and other modules you are using, how you have configured your Siebel applications, how you have deployed your applications, and other such factors also affect Siebel Application Object Manager performance and how many concurrent users you can support. Some of these factors include:
Hardware ResourcesHardware resources for each Siebel Server computer, particularly CPU and memory, are a factor in how many concurrent users can be supported for each Siebel Application Object Manager component. For example, a four-way computer has twice the resources of a two-way computer and can potentially support twice as many concurrent users. Key hardware resources for Siebel Application Object Manager performance include:
Disk I/O and network capacity are other important hardware factors, but they do not affect Siebel Application Object Manager tuning. They do significantly affect performance for the Siebel Database and the Siebel File System, which can severely impact the overall user response time. The total number of computers you can devote to supporting Siebel Application Object Manager components will determine the total number of concurrent users. |
Siebel Performance Tuning Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |