通过

64bit PowerShell performance in Orchestrator

  • 项目

imageSometimes you need to run a resource intensive PowerShell command using the ‘Run .Net Script’ activity. Problem is, Orchestrator is 32bit, and defaults to a 32bit PowerShell. What is the problem with this? 32bit processes can grow close to 2GB in memory. This is a hard limit. By using a 64bit process we break the 2GB barrier and gain performance.

Simply run your PowerShell script in a ScriptBlock as listed below. The –ScriptBlock forces 64bit PowerShell. Test and enjoy!

Invoke-Command -ComputerName localhost -ScriptBlock {
write-host "64bit speed!"
}

 

  jonjor