locked
Parallel PowerShell Remoting on > 500 nodes RRS feed

  • Question

  • Hi , 

    I want to understand the limitations of Invoke-Command . Can I trigger a Invoke-Command ( one to many ) on more than 500 nodes in parallel ? 

    If not possible , what are the alternatives ? 

    Thursday, March 8, 2018 1:36 PM

All replies

  • Try

    https://github.com/proxb/PoshRSJob

    or

    https://github.com/RamblingCookieMonster/Invoke-Parallel

    and increase the number of parallel actions until your cpu is at 100%

    Thursday, March 8, 2018 1:56 PM
  • There's a 'ThrottleLimit' parameter that you can adjust.


    • Edited by JS2010 Thursday, March 8, 2018 3:14 PM
    Thursday, March 8, 2018 3:14 PM
  • You can use Invoke-Command against 500+ nodes. Its developed keeping these requirements in mind.

    You can control the concurrency using -ThrottleLimit paramterer.

    PoshRSJob uses threads, where we won't be able to do everything what Invoke-Command  can do.


    Regards kvprasoon

    • Proposed as answer by jrv Thursday, March 8, 2018 11:42 PM
    Thursday, March 8, 2018 6:33 PM
  • Try

    https://github.com/proxb/PoshRSJob

    or

    https://github.com/RamblingCookieMonster/Invoke-Parallel

    and increase the number of parallel actions until your cpu is at 100%

    Remote jobs run in parallel.  They do not use much CPU.  Runspaces are not designed to do remote jobs.  They can be deigned to do this but I have yet to see code that does this.

    Invoke-Command can be designed to create disconnected sessions.  You can reconnect to the remote session and return the results at any later time.

    CPU and memory for disconnected remote jobs is trivil and can be in the thousands with little impact.


    \_(ツ)_/

    Thursday, March 8, 2018 11:46 PM