Real-time sensor dashboard in Raspberry Pi - Time & Space Complexity

Time Complexity: Real-time sensor dashboard

O(n)

Understanding Time Complexity

When building a real-time sensor dashboard on a Raspberry Pi, it's important to understand how the program's speed changes as more sensor data comes in.

We want to know how the time to update the dashboard grows when the number of sensors increases.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

while True:
    sensor_values = []
    for sensor in sensors:
        value = sensor.read()
        sensor_values.append(value)
    display.update(sensor_values)
    sleep(1)

This code reads data from each sensor, updates the dashboard display with all values, and repeats every second.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through all sensors to read their values.
• How many times: Once every second, the loop runs once over all sensors.

How Execution Grows With Input

As the number of sensors increases, the time to read and update grows proportionally.

Input Size (n)	Approx. Operations
10 sensors	10 reads + 1 update
100 sensors	100 reads + 1 update
1000 sensors	1000 reads + 1 update

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

Final Time Complexity

Time Complexity: O(n)

This means the time to update the dashboard grows in a straight line as you add more sensors.

Common Mistake

[X] Wrong: "Reading all sensors happens instantly no matter how many sensors there are."

[OK] Correct: Each sensor read takes time, so more sensors mean more total reading time.

Interview Connect

Understanding how your program scales with input size shows you can write efficient code that works well as projects grow.

Self-Check

"What if the dashboard only updated every 5 seconds instead of every second? How would the time complexity change?"