Skip to main content

Parallel Processing example using PowerShell

PowerShell version 7 has option to run tasks in Parallel. 

This would mean that task that can be run in Parallel mode and tasks can be done simultaneously and save time. 

How to get started or making use of Parallel in PowerShell? 

First, PowerShell has to be in version 7. 

Version 7 of PowerShell can be downloaded from Microsoft via this link below. 


Choose the version, whether its x86 or x64. 

The CPU architecture in your system will determine whether x64 PowerShell can be used or not. 

Check out this link to check CPU architecture in your system: Check if 64 bit processor or 32 bit

Sample code below, shows how Parallel processing in PowerShell can be done. 

  $HostsIPs = '127.0.0.1','8.8.8.8','8.8.4.4','1.1.1.1' 
  $HostsIPs | ForEach-Object -Parallel { 
    Test-Connection $_  
   } -ThrottleLimit 5 

The screenshot image below, shows that the commands indeed were processed in a Parallel mode since it was executed simultaneously. 





The number on the left side shows number "3", or "4". 

In which it shows that all the commands were executed at the same time. 

This code below shows how to execute same function as above but not using Parallel Processing.

$HostsIPs = '127.0.0.1','8.8.8.8','8.8.4.4','1.1.1.1'
$HostsIPs | ForEach-Object  { 
Test-Connection $_
}


The screenshot image below which does not utilize the Parallel processing, shows that the commands were executed one after the other. 





The number on the left side shows that the commands were executed in an orderly fashion, as it shows "1", "2", "3" and "4". 

So, PowerShell Parallel processing is quite awesome. 

But yes, not all tasks can be run in Parallel mode, especially if the task needs to wait the output of the previous command before it can run or execute. 

However, if commands can utilize Parallel processing then I guess that would be the best option since it will save a lot of time at the expense of the processing resources in your system.


 Cheers! Till next Time.

 Till next time. Stay safe! and keep things up! 

Do ASAP, Always Say A Prayer...

Practice O.T.G. = Obedience TGod

================================

Free Android Apps:

Click  links below to find out more:

Free Android Apps:

Click  links below to find out more:

Excel Keyboard guide:

https://play.google.com/store/apps/details?id=chrisjoms.myexcelapplicationguide

Heaven's Dew Fall  Prayer app for Android :

https://play.google.com/store/apps/details?id=soulrefresh.beautiful.prayer

Catholic Rosary Guide  for Android:

Pray the Rosary every day, countless blessings will be showered upon your life if you recite the Rosary faithfully. 

https://play.google.com/store/apps/details?id=com.myrosaryapp

Divine Mercy Chaplet Guide (A Powerful prayer) BFF = Be Filled Faith:

https://play.google.com/store/apps/details?id=com.dmercyapp  

Comments

Popular posts from this blog

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...

PowerShell Match Drive Letter to Volume ID in AWS

Matching AWS volume ID to its corresponding Windows drive letter is an easy task using PowerShell. Win32_DiskDrive holds the info for the volume-ID. Here’s the script, below enjoy 😊 $get_disks = gwmi -query "SELECT * FROM Win32_DiskDrive" ForEach ( $disk in $get_disks ){         $get_partitions = gwmi -query "ASSOCIATORS OF {Win32_DiskDrive.DeviceID=' $( $disk . DeviceID) '} WHERE AssocClass = Win32_DiskDriveToDiskPartition"     ForEach ( $partition in $get_partitions ){         $get_logicaldisks = gwmi -query "ASSOCIATORS OF {Win32_DiskPartition.DeviceID=' $( $partition . DeviceID) '} WHERE AssocClass = Win32_LogicalDiskToPartition"          ForEach ( $logicaldisk in $get_logicaldisks ){         $insert_the_dash = ( $disk . SerialNumber) . Insert( 3 , "-" ) #insert dash to match AWS v...

Delete Directories with Wildcards using rd or rmdir

  Deleting files in command prompt using wildcards is quite straight forward. Command below will delete all text (".txt") files on the specified path.      Del D:\txtlog\*.txt Command above will delete all files with ".txt" extension in d:\txtlog directory. Easy enough to delete all matching files. Using the same method with rmdir or rd command this will not work. For example, if we have a directory on d drive that is auto-generated by an application and the filename is consistent with a pattern plus incrementing number at the end to differentiate the folder from other folders.    D:\baklogs\log1\    D:\baklogs\log2\    D:\baklogs\log3\    Etc..    D:\baklogs\log100\ The folder name has a consistent pattern that is preceded by the word “log” plus incrementing number. If the command below is executed to remove the directories in one go, an error is shown which h...