First PowerShell command - Time & Space Complexity

Time Complexity: First PowerShell command

O(n)

Understanding Time Complexity

When we run a PowerShell command, it takes some time to finish. Understanding how this time changes as we give more work helps us write better scripts.

We want to know: how does the time to run the command grow when we change the input size?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

Get-Process | Where-Object { $_.CPU -gt 100 }

This command gets all running processes and filters those using more than 100 CPU seconds.

Identify Repeating Operations

• Primary operation: Checking each process one by one to see if its CPU usage is greater than 100.
• How many times: Once for every process running on the system.

How Execution Grows With Input

As the number of processes increases, the command checks each one, so the work grows steadily.

Input Size (n)	Approx. Operations
10	10 checks
100	100 checks
1000	1000 checks

Pattern observation: The number of checks grows directly with the number of processes.

Final Time Complexity

Time Complexity: O(n)

This means the time to run the command grows in a straight line as the number of processes grows.

Common Mistake

[X] Wrong: "The command runs instantly no matter how many processes there are."

[OK] Correct: The command must check each process, so more processes mean more work and more time.

Interview Connect

Knowing how commands scale with input size helps you write scripts that stay fast even when data grows. This skill shows you understand how computers handle work.

Self-Check

"What if we added another filter inside the command? How would the time complexity change?"