How to configure runbook throttling
Important
This version of Orchestrator has reached the end of support. We recommend you to upgrade to Orchestrator 2022.
You can adjust the number of runbooks that are run concurrently on a runbook server. Reducing the number is known as runbook throttling. By default, each runbook server is configured to simultaneously run a maximum of 50 runbooks. You can change this number by using the Runbook Server Runbook Throttling tool. In most cases, you can keep this default setting, but you should consider the resource requirements of the runbooks on a particular server when considering whether to change it. If the server has many runbooks with high resource requirements, you might run fewer runbooks simultaneously on the runbook server. If they're simple runbooks with minimal requirements, you might consider increasing the number of simultaneously run runbooks.
Configure the maximum number of runbooks that a runbook server processes
Follow these steps to configure the maximum number of runbooks that a runbook server processes:
- Navigate to the folder whereby default the Runbook Server Runbook Throttling tool is stored:
C:\Program Files (x86)\Microsoft System Center\Orchestrator\Management Server
.
- Navigate to the folder whereby default the Runbook Server Runbook Throttling tool is stored:
C:\Program Files\Microsoft System Center\Orchestrator\Management Server
.
Enter one of the following commands:
To apply the change to one runbook server:
aspt <RunbookServerName> <MaximumRunningRunbooks>.
For example, to set the maximum number of runbooks that RunbookServer1 runs to 40:
aspt RunbookServer1 40
To apply the change to all runbook servers:
aspt * <MaximumRunningRunbooks>.
For example, to set the maximum number of runbooks that all runbook servers run to 40:
aspt * 40
Restart the Orchestrator Runbook Service.
Next steps
Learn more about optimizing Orchestrator performance at Database sizing and performance.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for