Yes, there are many reasons to create more than one process schedulers on a single host. The below mentioned suggestions are for the sites which has high volume of processes like Procurement or CRM.

1. For some reason if a process scheduler is struck, and you are not able to restart that process scheduler, you do not want the jobs queued up on one scheduler, and you want to have another scheduler if you want keep as failover instead of creating a new one at that point in time.
2. If you are running multiple processes which run on different recurrence, you would like to run them in different process schedulers to ensure that the more frequent running processes don't have to wait in queue when a long running processes are running and also if you have some important processes which should not be going through the regular queue process and wait for the long running other less important processes to complete.
3. Also when you are setting up process schedulers, you can set up maximum concurrent process that can run on each process scheduler depending on the load on to system type of process you run on by manipulating psprcs.cfg for PSAESRV or other servers with Max Instances parameter and on PIA by navigating to People Tools --> Process Scheduler -->Servers -->Server Definition page with max concurrent processes for each type of processes.
4. Also another reason would be create more than one distribution nodes, if you are having high distribution sites. [Example: sites which runs more than 30000 processes in a week and have report distribution and workflow combination]  It is better to have more than one process scheduler to divide the distribution load between the nodes and also if you have a SSL distribution node and with https connection for secured reports and http node for non secured reports, you want to keep it separate even though you can route both through https.
5. Another reason I have used multiple process scheduler is that you want to hold a set of processes for some reason you could bring down the process scheduler on which the processes are scheduled rather than putting all the queued processes on hold individually, when you have only one process scheduler. Also if you have configured “Scheduled job Sets” which gets queued at the scheduled time unlike the recurrence jobs which scheduled once the previous job completed, it is better to have the process scheduler down rather than putting each job set into “inactive” mode one by one.

Comments (1)

	1. 02-06-2008 20:13
	Good Posting Guest

Mike

Write Comment

Thankyou for your comments. Feel free to comment if there are any mistake in the postings also. If you have a Blog or website, feel free to provide the link. We will take a peak. Just ensure to *Refresh* your browser for a new security code to be displayed prior to clicking on the 'Send' button. Keep in mind that the above process only applies if you simply entered the wrong security code.
Name:
Homepage
BBCode:
Comment:
Code:*
	I wish to be contacted by email regarding additional comments

Copy Right: AKOComments v.1.4.6