Why process control manages execution in Bash Scripting - Performance Analysis

Time Complexity: Why process control manages execution

O(n)

Understanding Time Complexity

When we use process control in bash scripts, it affects how commands run one after another.

We want to see how this control changes the time the script takes as it runs more commands.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

for file in *.txt; do
  grep "pattern" "$file" > /dev/null
  if [ $? -eq 0 ]; then
    echo "$file contains pattern"
  fi
  sleep 1
 done
    

This script checks each text file for a pattern, prints a message if found, and waits 1 second before the next file.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for-loop that goes through each text file.
• How many times: Once for every file matching *.txt in the folder.

How Execution Grows With Input

Explain the growth pattern intuitively.

Input Size (n)	Approx. Operations
10	About 10 grep checks and 10 sleep waits
100	About 100 grep checks and 100 sleep waits
1000	About 1000 grep checks and 1000 sleep waits

Pattern observation: The total time grows directly with the number of files because each file adds the same steps.

Final Time Complexity

Time Complexity: O(n)

This means the script's running time grows in a straight line as the number of files increases.

Common Mistake

[X] Wrong: "Process control commands like sleep don't affect overall time complexity."

[OK] Correct: Even simple commands like sleep add fixed time per loop, so they increase total time as input grows.

Interview Connect

Understanding how process control affects execution time helps you write scripts that run efficiently and predictably, a useful skill in many real-world tasks.

Self-Check

"What if we removed the sleep command? How would the time complexity change?"