Integer variables in Bash Scripting - Time & Space Complexity

Time Complexity: Integer variables

O(n)

Understanding Time Complexity

We want to see how the time to run a bash script changes when it uses integer variables.

Specifically, we ask: does using integer variables affect how long the script takes as it runs?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

#!/bin/bash

count=0
for i in {1..1000}
do
  ((count = count + 1))
done

echo "Count is $count"
    

This script uses an integer variable count and increments it 1000 times in a loop.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Incrementing the integer variable count inside the loop.
• How many times: Exactly 1000 times, once per loop iteration.

How Execution Grows With Input

As the number of loop iterations grows, the number of increments grows the same way.

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

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

Final Time Complexity

Time Complexity: O(n)

This means the time to run the script grows in a straight line as the number of increments increases.

Common Mistake

[X] Wrong: "Using integer variables makes the script run instantly, no matter how many times it loops."

[OK] Correct: Even though integers are simple, the script still does one increment per loop, so time grows with the number of loops.

Interview Connect

Understanding how simple operations like integer increments scale helps you explain script efficiency clearly and confidently.

Self-Check

"What if we replaced the loop with a nested loop that increments the variable inside both loops? How would the time complexity change?"