This runbook can be used to experiment with different configurations of Orchestrator. For example, supposed you wanted to determine the performance of four Runbook Servers deployed to different data centers. Data Center Logging Platform Code ms/Activity Scale Factor Configuration Run Time (seconds) Location 1 Default logging 819 82 1.0 (reference) Location 1 Logging common 2012 201 2.5 published data Location 2 Default logging 1229 123 1.5 Location 2 Logging common 3686 369 4.5 published data Location 3 Default logging 2457 426 3.0 Location 3 Logging common 4422 442 5.4 published data Location 4 Default logging 1474 147 1.8 Location 4 Logging common 2654 265 3.2 published data Notice the significant decrease in platform performance caused by logging of common published data. The worst scenario appears to be logging of common published data at Location 2. On the surface, this appears to be a clear and relevant conclusion. However, it should be noted that these figures reflect the overhead of the platform code, not the domain code. Domain code runtimes can be significantly longer. For example, the Create VM from Template activity in the Virtual Machine Manager Integration Pack may run for several minutes as the VM is created. Expanding on the previous example, consider the platform code costs on a runbook activity that takes 1 minute to run (1 minute = 60,000 milliseconds) regardless of location. Data Center Logging Platform Code % Domain Code % Platform Code Configuration Run Time (seconds) Location 1 Default logging 819 98.6% 1.4%
This runbook can be used to experiment with different configurations of Orchestrator. For example, supposed you wanted to determine the performance of four Runbook Servers deployed to different data centers. Data Center Logging Configuration Platform Code Run Time (seconds) ms/Activity Scale Factor Location 1 Default logging 819 82 1.0 (reference) Location 1 Logging common published data 2012 201 2.5 Location 2 Default logging 1229 123 1.5 Location 2 Logging common published data 3686 369 4.5 Location 3 Default logging 2457 426 3.0 Location 3 Logging common published data 4422 442 5.4 Location 4 Default logging 1474 147 1.8 Location 4 Logging common published data 2654 265 3.2 Notice the significant decrease in platform performance caused by logging of common published data. The worst scenario appears to be logging of common published data at Location 2. On the surface, this appears to be a clear and relevant conclusion. However, it should be noted that these figures reflect the overhead of the platform code, not the domain code. Domain code runtimes can be significantly longer. For example, the Create VM from Template activity in the Virtual Machine Manager Integration Pack may run for several minutes as the VM is created. Expanding on the previous example, consider the platform code costs on a runbook activity that takes 1 minute to run (1 minute = 60,000 milliseconds) regardless of location. Data Center Logging Configuration Platform Code Run Time (seconds) % Domain Code % Platform Code Location 1 Default logging 819 98.6% 1.4%