Progress indicators in Bash Scripting - Time & Space Complexity

Time Complexity: Progress indicators

O(n)

Understanding Time Complexity

When we add progress indicators in bash scripts, we want to know how much extra work they add as the task grows.

We ask: How does showing progress affect the script's running time as input size increases?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

#!/bin/bash

count=0
for file in /path/to/files/*; do
  # Process each file
  echo "Processing $file"
  ((count++))
  # Show progress every 10 files
  if (( count % 10 == 0 )); then
    echo "Processed $count files so far..."
  fi
done

This script processes files one by one and prints a progress message every 10 files.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping over each file in the directory.
• How many times: Once per file, so as many times as there are files (n).
• Progress check: Every 10 files, a message is printed (about n/10 times).

How Execution Grows With Input

As the number of files grows, the script processes each file once and prints progress messages occasionally.

Input Size (n)	Approx. Operations
10	10 file processes + 1 progress message
100	100 file processes + 10 progress messages
1000	1000 file processes + 100 progress messages

Pattern observation: The main work grows linearly with n, and progress messages grow much slower, about n divided by 10.

Final Time Complexity

Time Complexity: O(n)

This means the script's running time grows directly in proportion to the number of files processed.

Common Mistake

[X] Wrong: "Printing progress every file makes the script much slower, changing the time complexity."

[OK] Correct: Printing progress messages adds some work, but it happens at fixed intervals, so it doesn't change the overall linear growth with input size.

Interview Connect

Understanding how progress indicators affect script speed shows you can balance user feedback with efficiency, a useful skill in real scripting tasks.

Self-Check

"What if we printed a progress message after processing every single file instead of every 10 files? How would the time complexity change?"

Practice

1. What is the main purpose of using a progress indicator in a bash script?

easy

A. To print all output to a file instead of the screen

B. To speed up the execution of the script

C. To stop the script if an error occurs

D. To show the user that a long-running task is still working

Solution

1. Step 1: Understand what progress indicators do

   Progress indicators provide visual feedback during long tasks to reassure users the script is running.

2. Step 2: Identify the correct purpose

   Among the options, only showing the user the task is still working matches the purpose of progress indicators.

3. Final Answer:

   To show the user that a long-running task is still working -> Option D

4. Quick Check:

   Progress indicator purpose = show task progress [OK]

Hint: Progress indicators show task status, not speed or errors [OK]

Common Mistakes:

• Thinking progress indicators speed up scripts
• Confusing progress indicators with error handling
• Assuming progress indicators redirect output

2. Which of the following bash code snippets correctly updates the same line to show a spinner?

easy

A. echo -ne "|\r"; sleep 1; echo -ne "/\r"

B. echo "|"; sleep 1; echo "/"

C. echo -n "|"; sleep 1; echo -n "/"

D. echo -e "|\n"; sleep 1; echo -e "/\n"

Solution

1. Step 1: Understand how to update the same line in bash

   Using echo -ne with \r returns the cursor to the start of the line to overwrite it.

2. Step 2: Check each option for correct usage

   echo -ne "|\r"; sleep 1; echo -ne "/\r" uses echo -ne "|\r" and echo -ne "/\r", which updates the same line. Others print new lines or lack -e or -n.

3. Final Answer:

   echo -ne "|\r"; sleep 1; echo -ne "/\r" -> Option A

4. Quick Check:

   Use echo -ne with \r to update line [OK]

Hint: Use echo -ne and \r to overwrite the same line [OK]

Common Mistakes:

• Using echo without -n or -e flags
• Using \n instead of \r to update line
• Printing spinner on new lines instead of same line

3. What will be the output of this bash snippet?

for i in {1..3}; do
  echo -ne "Processing $i...\r"
  sleep 1
done
echo "Done!"

medium

A. Processing 1...
Processing 2...
Processing 3...
Done!

B. Processing 3...
Done!

C. Processing 1...Processing 2...Processing 3...Done!

D. Done!
Processing 3...

Solution

1. Step 1: Understand echo -ne with \r inside the loop

   Each loop iteration prints 'Processing i...' and returns cursor to line start, overwriting previous output.

2. Step 2: Determine final visible output after loop

   Only the last 'Processing 3...' remains visible, then 'Done!' prints on a new line.

3. Final Answer:

   Processing 3... Done! -> Option B

4. Quick Check:

   \r overwrites line, last iteration visible [OK]

Hint: Remember \r returns cursor, overwriting previous line [OK]

Common Mistakes:

• Thinking all lines print separately
• Confusing \r with \n
• Ignoring that echo -ne prevents newline

4. Identify the error in this bash spinner script snippet:

spinner="|/-\\"
while true; do
  for i in $(seq 0 3); do
    echo -ne "${spinner:$i:1}\r"
    sleep 0.2
done
done

medium

A. The script will cause an infinite loop without exit

B. The for loop uses incorrect sequence range

C. The spinner string is missing characters

D. The substring syntax ${spinner:$i:1} is invalid in bash

Solution

1. Step 1: Analyze the loop structure

   The outer while true loop runs forever without any exit condition.

2. Step 2: Check for exit or break statements

   No break or exit is present, so the spinner runs infinitely, which may be unintended.

3. Final Answer:

   The script will cause an infinite loop without exit -> Option A

4. Quick Check:

   while true without break causes infinite loop [OK]

Hint: Check loops for exit conditions to avoid infinite loops [OK]

Common Mistakes:

• Assuming infinite loops are errors always
• Confusing substring syntax with error
• Ignoring that spinner string is correct

5. You want to create a progress bar in bash that fills from 0% to 100% in 10 steps, updating on the same line. Which approach correctly implements this?

hard

A. Use echo without -n or -e flags inside the loop to print progress

B. Print all '#' characters at once, then sleep 10 seconds

C. Use a loop from 1 to 10, print '#' repeated i times with echo -ne and \r, then sleep

D. Use multiple echo commands without \r to print progress on new lines

Solution

1. Step 1: Understand progress bar update method

   To update on the same line, use echo -ne with \r to overwrite the line each iteration.

2. Step 2: Implement loop with repeated '#' characters

   Loop from 1 to 10, print '#' repeated i times, then sleep to simulate progress.

3. Final Answer:

   Use a loop from 1 to 10, print '#' repeated i times with echo -ne and \r, then sleep -> Option C

4. Quick Check:

   Loop + echo -ne + \r = progress bar update [OK]

Hint: Use echo -ne with \r and repeated chars in loop [OK]

Common Mistakes:

• Printing progress on new lines instead of same line
• Not using echo -n or -e flags
• Printing all progress at once without updates