Siebel Field Service Guide > Scheduling Using Siebel Scheduler >

About Enhancing the Performance of Siebel Scheduler

Each Siebel Server can run 1 or more service regions. Large service regions can run on a dedicated server.

Each service region can run on only 1 application server so that the information for 1 service region is cached in memory instead of continually read from the Siebel database, reducing the load on the Siebel database during schedule optimization.

CAUTION:  It is recommended that you include no more than 400 service regions on 1 physical server because of the limitations on the Server Request Broker scalability. If your service regions exceed that amount for the ABS or Optimizer, then you must test performance and scalability carefully. For more information, see About Siebel Scheduler and the Server Request Broker.

The ABS and Optimizer interact with the Siebel database only for the following functionality:

• Data loading. The ABS and Optimizer read large amounts of information from the Siebel database on start up, or when the service region is reloaded. Therefore, avoid reloading during a busy time. For more information, see About Loading and Reloading Data for Service Regions.
• Saving schedules. The Optimizer can save its result sets to the Siebel database at specified time intervals. Unless the data set is very large, the Optimizer does not noticeably affect Siebel database performance. For more information, see the Optimizer - Save Interval parameter in Table 11.

CAUTION:  Although acceptable for testing, it is recommended that you keep the Siebel Application Object Manager and the Siebel Scheduler components on separate computers in the production environment to prevent surges in user activity from hindering the Siebel Scheduler operations.

Balance of the CPU Load for Service Regions

In general, the number of processes must be less than or equal to the number of CPUs on the server because the operating system (OS) farms out the work on each process to a separate CPU. When a small number of service regions exist, include each service region on a separate process number in a server. When the number of service regions exceeds the number of CPUs, and when each service region is approximately the same size, divide the regions equally across the processes. If the service regions are not the same size, then balance the regions according to size. For example, put a 50-person service region on Process 1 and two 25-person service regions on Process 2. Another way to load balance is to note the amount of time to load and aim for an equivalent amount of load time on each process.

NOTE:  You cannot specify the CPU for a process. The OS indicates this specification. It generally has its own algorithms to maximize performance in a multi-CPU environment.