Why redundancy prevents costly downtime in SCADA systems - Performance Analysis

Time Complexity: Why redundancy prevents costly downtime

O(n)

Understanding Time Complexity

We want to understand how adding redundancy affects system response time during failures.

How does redundancy change the time cost when something goes wrong?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

// Check primary sensor status
if (sensor_primary.isActive()) {
  readData(sensor_primary);
} else {
  // Switch to backup sensor if primary fails
  readData(sensor_backup);
}
processData();

This code reads data from a primary sensor if it is active; otherwise, it switches to a backup sensor to avoid downtime.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Reading data from one sensor at a time.
• How many times: Once per data cycle, either from primary or backup sensor.

How Execution Grows With Input

Execution time grows linearly with the number of data cycles, regardless of redundancy.

Input Size (n)	Approx. Operations
10	10 sensor reads
100	100 sensor reads
1000	1000 sensor reads

Pattern observation: The system reads data once per cycle, switching sensors if needed, so time grows steadily with input size.

Final Time Complexity

Time Complexity: O(n)

This means the time to process data grows directly with the number of data cycles, even with redundancy in place.

Common Mistake

[X] Wrong: "Adding a backup sensor doubles the time needed for data reading."

[OK] Correct: Only one sensor is read per cycle, so redundancy does not double the time; it just provides a fallback without extra cost per cycle.

Interview Connect

Understanding how redundancy affects time helps you explain system reliability without extra delays, a key skill in real-world system design.

Self-Check

"What if the system read from both primary and backup sensors every cycle? How would the time complexity change?"