Load Balancing Among PeopleSoft Process Scheduler Domains
You may be making use of multiple process scheduler domains for the purpose of load distribution but you may not have observed this -- Some domains would be taking most of the work where other domains may not be processing as much or hardly doing any work at all!
There are quite a few ways in which you can do work load distribution between multiple PeopleSoft Process Scheduler Domains. One of the easiest out-of-the-box option is to make use of the Master Scheduler.
However, you may be surprised to hear that one of the biggest misconceptions of the load balancing feature of the Master Scheduler is that work will be distributed evenly among the available process schedulers.
The predetermined Primary OS, by default, receives a majority of the work.
This means that all the process scheduler domains created in the Primary OS will be considered and assigned work first, as configured, and this is as designed.
Also, it is interesting to note that the work coming in is assigned to different servers based on their boot order ranking, so the first server in a particular OS to boot would be considered first in the list for work when work is available for that OS and the server has an open slot for that type of work.
Round robin assignment of load balanced requests only occurs when multiple process requests to be load balanced are to be scheduled simultaneously (so groups of processes of 2 or more).
If you would like to improve the work load distribution between different proceess scheduler domains, consider adding/removing the following aspects as well:
1. Using run controls that designate a specific server
2. Server Definition configuration for accepting load balance work
3. Recurrences scheduled on a particular server
4. Process Definition/Type OS restrictions
5. Server Definition configuration for redistributing work load
6. Server Definition configuration of Max Concurrent for processes and categories
Note: Load balancing occurs only for process requests where the server name is not specifically specified in the process definition.
