Why variables store and reuse data in Bash Scripting - Performance Analysis

Time Complexity: Why variables store and reuse data

O(n)

Understanding Time Complexity

We want to see how using variables affects the speed of a bash script.

Specifically, does storing and reusing data in variables change how long the script takes as it runs?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

count=0
for file in /path/to/files/*; do
  size=$(stat -c%s "$file")
  count=$((count + size))
done

echo "Total size: $count bytes"
    

This script loops over files, stores each file size in a variable, and adds it to a total.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping over each file and getting its size.
• How many times: Once for every file in the folder.

How Execution Grows With Input

Each file adds one more loop step and one more variable update.

Input Size (n)	Approx. Operations
10	About 10 size checks and additions
100	About 100 size checks and additions
1000	About 1000 size checks and additions

Pattern observation: The work grows directly with the number of files.

Final Time Complexity

Time Complexity: O(n)

This means the script takes longer in a straight line as you add more files.

Common Mistake

[X] Wrong: "Using variables makes the script run faster by skipping work."

[OK] Correct: Variables just store data to reuse, but the script still does the same number of steps for each file.

Interview Connect

Understanding how variables affect script speed helps you write clear and efficient automation scripts.

Self-Check

What if we stored all file sizes in an array instead of one variable? How would the time complexity change?