Скачать или смотреть Optimize Your PowerShell Command: Speed Up Calculated Properties in Firewall Rule Queries

Discover effective strategies to optimize PowerShell commands for faster execution when using calculated properties, specifically in querying firewall rules and ports.
---
This video is based on the question https://stackoverflow.com/q/68438128/ asked by the user 'Lhakryma DL' ( https://stackoverflow.com/u/11020882/ ) and on the answer https://stackoverflow.com/a/68439154/ provided by the user 'Theo' ( https://stackoverflow.com/u/9898643/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Speed up powershell command when using calculated properties

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Speeding Up PowerShell Commands with Calculated Properties

If you've ever worked with PowerShell, you know that efficiency is key. Recently, I encountered a common problem when listing firewall rules and ports using calculated properties. The initial command I wrote was slow and inefficient due to repeated calls to Get-NetFirewallRule. In this post, I'll share my experience and guide you through optimizing PowerShell commands to achieve faster results.

The Initial Challenge

When attempting to list firewall rules and their associated ports, I started with these two commands:

Get-NetFirewallRule

Get-NetFirewallPortFilter

To filter the results down to numerical ports only, I constructed the following PowerShell command:

[[See Video to Reveal this Text or Code Snippet]]

While this command worked, I soon realized the performance was lacking. I timed its execution, and it generated about three lines per second—far too slow for my requirements.

Result from Timing the Command:

Time Taken: 119 seconds

Total Lines Outputted: 358

Clearly, something needed to change to enhance performance.

Optimizing the Command

To speed up the execution of this command, the primary optimization tactic is to eliminate repetitive calls to Get-NetFirewallRule. Instead of calling it multiple times for each port filter, we can store the result of this command in a variable and refer to it later. Below, I will outline the steps to accomplish this:

Revised Command using ForEach-Object

Here’s an optimized version of my original command, using ForEach-Object:

[[See Video to Reveal this Text or Code Snippet]]

Further Optimization with foreach()

It might be even more efficient to replace ForEach-Object with a foreach() loop. This minor change can potentially slightly speed up the command, as shown below:

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

By reformulating how you handle commands within PowerShell, particularly when dealing with calculated properties, you can significantly enhance performance. By reducing the number of calls to Get-NetFirewallRule, the execution time will improve remarkably.

Implement these optimizations in your PowerShell scripts when listing firewall rules to enjoy faster, smoother executions. It’s a simple tweak that makes a world of difference!