Multiple Processor Support
If the underlying operating system can support multiple processors on 1 computer, then Siebel Scheduler can take advantage of the processors by running different service regions for the ABS and Optimizer on different processors. You must set different process numbers in a server key mapping. A server with a single processor can run multiple processes, but this setup can adversely affect performance. Service regions in different processes are run in parallel, while service regions in the same process are run serially.
Because the ABS and Optimizer are different modules, they are already running as separate processes, even though the process number is the same. A module for 1 service region can run in only 1 process at a time.
For example, consider a 4-processor computer with only 2 processors in use. The following table shows an example of the key mapping when 1 service region runs with both the ABS and Optimizer. Process refers to the number of processes for that component, not the processor number on the server.
Server | Service Region | Process | Module |
---|---|---|---|
AppServer1 |
West Coast Region |
1 |
ABS |
AppServer1 |
West Coast Region |
1 |
Optimizer |
You cannot run 1 module for a service region as 2 processes.
The following table shows an example of the key mapping when 2 service regions run on a 4-processor computer. In this example, you can use all 4 processors. Process refers to the number of processes for that component, not the processor number on the server.
Server | Service Region | Process | Module |
---|---|---|---|
AppServer1 |
West Coast Region |
1 |
ABS |
AppServer1 |
East Coast Region |
2 |
ABS |
AppServer1 |
West Coast Region |
1 |
Optimizer |
AppServer1 |
East Coast Region |
2 |
Optimizer |
If there are more than 2 service regions on a 4-processor computer, then you can run the modules as different processes. The following table shows an example of the key mapping for the best use of the processors on a server when the West Coast Region is very large and the Central Region and East Coast Region are smaller. Process refers to the number of processes for that component, not the processor number on the server.
Server | Service Region | Process | Module |
---|---|---|---|
AppServer1 |
West Coast Region |
1 |
ABS |
AppServer1 |
East Coast Region |
2 |
ABS |
AppServer1 |
Central Region |
2 |
ABS |
AppServer1 |
West Coast Region |
1 |
Optimizer |
AppServer1 |
East Coast Region |
2 |
Optimizer |
AppServer1 |
Central Region |
2 |
Optimizer |
The West Coast Region requires more computation and uses 2 processors. The East Coast Region and Central Region run in the same processes and on the same 2 processors.
Each server component is multithreaded and can load schedules for multiple service regions. Multiple threads can share these schedules. Each request to the Optimizer runs on a new thread.
A request identifies the required schedule for 1 service region and locks the schedule. Requests for schedules for other service regions can continue while requests for the same schedule are queued. Because the response time for the ABS is fast, high latency for the returned booking times does not result because the processing time between ABS transactions is usually several minutes.