Configure the concurrent processing of actions
Please note that an administrative PowerShell console at the ScriptRunner Service host is required to run the cmdlets of the ScriptRunnerSettings module.
ScriptRunner can only process a certain amount of actions simultaneously (default 10) and differentiates between interactive and scheduled requests.
If all of these processing engines are busy, additional requests are written to a queue and processed as soon as engines become available again. If the use of this queue increases too much, only interactive requests will be accepted, so schedules have a lower priority than interactive requests.The execution speed of a script depends on the particular script.
The scheduler executes only one current request for each action; if this action runs very long or has to wait too long in the processing queue, following requests of this action are ignored.
This prevents high frequency schedules from overloading the queues, as long as the processing engines are occupied by very long running actions.
A complete allocation of all processing engines should be avoided, otherwise ScriptRunner can no longer react promptly to interactive requests from the apps, this applies especially to scripted queries.
If the ScriptRunner host has sufficient performance, the number of processing engines can be increased.
Set-AsrSettings -PSEngines 15 -Restart
The Restart parameter restarts the ScriptRunner service to apply changes immediately
In the folder C:\ProgramData\ScriptRunner\Service\Local\Engines
a subfolder is created for each Engine. The respective Engine creates their subfolder the first time it is used. The log files in each folder can be used to trace when this engine was in use.
The Windows Performance Monitor (PerfMon.msc) or the ScriptRunner Service Performance
Monitor can be used to monitor the usage of the ScriptRunner instance.
More information can be found here:
This page has been automatically translated and may contain grammatical errors or inaccuracies