|Bookshelf Home | Contents | Index | PDF|
It is critically important not to set the maximum number of tasks for an Application Object Manager (AOM) or other load-balanced component higher than the server can reasonably handle. The server component parameter MaxTasks, sets the maximum number of sessions an AOM or AOM thread can handle. Use this parameter to set an AOMs maximum workload ceiling.
For example, a Siebel Server can handle 400 tasks for an AOM without degraded performance, but you set the maximum tasks to 500. When the AOM reaches 400 tasks, new tasks continue to be accepted, but server performance begins to degrade noticeably. Load balancing becomes inefficient as tasks are sent to the over-tasked server.
For multithreaded components, MaxTasks specifies the number of tasks that can run within each thread. MaxMTServers specifies the number of threads that the component can run. The total number of tasks that a multithreaded component can run is MaxTasks multiplied by MaxMTServers.
|Deployment Planning Guide|