Options
SMA performance optimisation question - time to start
Leigh_Kilday
Member Ninja IT Monkey ✭✭✭✭
in SMA
We are using SMA, and our runbooks are exclusively PowerShell Scripts. From what I have found, using PowerShell Scripts instead of Workflows is the only suggestion for optimising the time to start.
I'm a bit disappointed by the average time to start for most of our runbooks. Our Production instance has 2 app servers load-balanced and we are not using the WAP at all. The average time to start for some runbooks is anywhere from 1:1 to 8:1 of the execution duration (time to start - time to finish).
I haven't looked into the volume of jobs over time yet, but runbook executions are <100 per day so I doubt it'd be overloaded. SMA servers are 8GB, 2 core @ 2.66GHz and never push their resources very hard.
I can't think of anything unique about the runbooks that start faster on average compared with those that start slower. Almost all create a remote session on the SCSM primary workflow server, and one of them is invoked by a Cireson PowerShell activity, while the others are invoked either by an SCSM workflow or a SMA RB activity. We have Log Verbose set on all runbooks because we are executing so few we aren't concerned about the associated DB growth.
However, I doubt any of that has an effect on the time to start; more likely the execution time.
Does anybody know how to speed this up?
I'm a bit disappointed by the average time to start for most of our runbooks. Our Production instance has 2 app servers load-balanced and we are not using the WAP at all. The average time to start for some runbooks is anywhere from 1:1 to 8:1 of the execution duration (time to start - time to finish).
I haven't looked into the volume of jobs over time yet, but runbook executions are <100 per day so I doubt it'd be overloaded. SMA servers are 8GB, 2 core @ 2.66GHz and never push their resources very hard.
I can't think of anything unique about the runbooks that start faster on average compared with those that start slower. Almost all create a remote session on the SCSM primary workflow server, and one of them is invoked by a Cireson PowerShell activity, while the others are invoked either by an SCSM workflow or a SMA RB activity. We have Log Verbose set on all runbooks because we are executing so few we aren't concerned about the associated DB growth.
However, I doubt any of that has an effect on the time to start; more likely the execution time.
Does anybody know how to speed this up?
0
Best Answers
-
Options
Matt_Medley
Member Advanced IT Monkey ✭✭✭
Hey Leigh, take a look at this blog link from Microsoft. They go over some great things regarding SMA / runbooks performance.Leigh_Kilday said:Hi Matt, no not directly. We have built our own module to simplify the scripts in CPAs and SMA runbooks, but they're just over the top of SMLets and the native CMDLets.
https://blogs.technet.microsoft.com/orchestrator/2014/02/24/configure-service-management-automation-for-optimum-performance/
6 -
OptionsLeigh_Kilday
Member Ninja IT Monkey ✭✭✭✭
The answer for us was to alter the sandbox values. As of this time I haven't been able to inspect the sandboxes to dig deeper, but we dramatically improved our time-to-start by running each runbook in its own sandbox.
There are settings in the Orchestrator.Settings.Config under The values used to configure the Activator which I assume has something to do with the time-to-start, but I've not played around with those values yet.1 -
OptionsMatt_Medley
Member Advanced IT Monkey ✭✭✭
I'm glad you were able to get this issue resolved. Thank you for providing the details as to what worked for you and thank you for using the Cireson Community!Leigh_Kilday said:The answer for us was to alter the sandbox values. As of this time I haven't been able to inspect the sandboxes to dig deeper, but we dramatically improved our time-to-start by running each runbook in its own sandbox.
There are settings in the Orchestrator.Settings.Config under The values used to configure the Activator which I assume has something to do with the time-to-start, but I've not played around with those values yet.5
Answers
https://blogs.technet.microsoft.com/orchestrator/2014/02/24/configure-service-management-automation-for-optimum-performance/
There are settings in the Orchestrator.Settings.Config under The values used to configure the Activator which I assume has something to do with the time-to-start, but I've not played around with those values yet.