Passive vs active buzzer difference in Arduino - Performance Comparison

Time Complexity: Passive vs active buzzer difference

O(n)

Understanding Time Complexity

When using buzzers in Arduino projects, it helps to know how their control affects program speed.

We want to see how the buzzer type changes the work the program does as input grows.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

// Active buzzer example
void playActiveBuzzer(int duration) {
  digitalWrite(8, HIGH); // turn buzzer on
  delay(duration);       // wait
  digitalWrite(8, LOW);  // turn buzzer off
}

// Passive buzzer example
void playPassiveBuzzer(int duration) {
  for (int i = 0; i < duration; i++) {
    tone(8, 1000);       // play tone
    delay(1);            // short delay
  }
  noTone(8);             // stop tone
}

This code plays sounds using an active buzzer and a passive buzzer differently.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The passive buzzer code uses a loop calling tone() many times.
• How many times: The loop runs once per millisecond of duration.

How Execution Grows With Input

As the duration grows, the active buzzer code waits but does not loop, while the passive buzzer code loops more.

Input Size (duration in ms)	Approx. Operations
10	10 tone calls (passive), 1 wait (active)
100	100 tone calls (passive), 1 wait (active)
1000	1000 tone calls (passive), 1 wait (active)

Pattern observation: Passive buzzer work grows with duration; active buzzer work stays about the same.

Final Time Complexity

Time Complexity: O(n)

This means the passive buzzer code takes longer as duration grows, while active buzzer code stays constant time.

Common Mistake

[X] Wrong: "Both buzzers take the same time to play a sound because they just wait."

[OK] Correct: The passive buzzer example code uses repeated tone calls in a loop, so the program runs more steps as duration grows, unlike the active buzzer.

Interview Connect

Understanding how hardware choices affect program steps helps you write efficient code and explain your design decisions clearly.

Self-Check

"What if we replaced the delay(1) inside the passive buzzer loop with a delay(10)? How would the time complexity change?"