set -x for trace mode in Bash Scripting - Time & Space Complexity

Time Complexity: set -x for trace mode

O(n)

Understanding Time Complexity

We want to see how turning on trace mode with set -x affects the running time of a bash script.

Does tracing slow down the script as input grows?

Scenario Under Consideration

Analyze the time complexity of this bash script with tracing enabled.

#!/bin/bash
set -x

for i in $(seq 1 "$1"); do
  echo "Number: $i"
done

This script prints numbers from 1 to the input number, showing each command as it runs because of set -x.

Identify Repeating Operations

Look at what repeats in this script.

• Primary operation: The for loop runs echo commands repeatedly.
• How many times: Exactly as many times as the input number n.
• Trace output: Each command is printed before execution, adding extra steps.

How Execution Grows With Input

As the input number grows, the script runs more commands and prints more trace lines.

Input Size (n)	Approx. Operations
10	About 20 (10 echo + 10 trace lines)
100	About 200 (100 echo + 100 trace lines)
1000	About 2000 (1000 echo + 1000 trace lines)

Pattern observation: The total steps roughly double because each command is traced before running.

Final Time Complexity

Time Complexity: O(n)

This means the time grows linearly with the input size, even with tracing on.

Common Mistake

[X] Wrong: "Turning on set -x makes the script run in constant time because it just prints commands."

[OK] Correct: Actually, tracing adds extra output for every command, so the total work grows with how many commands run.

Interview Connect

Understanding how debugging tools like set -x affect script speed helps you write efficient scripts and explain your reasoning clearly in interviews.

Self-Check

"What if we only enabled set -x inside the loop? How would that change the time complexity?"