Why data logging matters for IoT in Raspberry Pi - Performance Analysis

Time Complexity: Why data logging matters for IoT

O(n)

Understanding Time Complexity

When working with IoT devices like Raspberry Pi, data logging collects sensor readings over time. We want to understand how the time to save data grows as more readings are collected.

How does the time needed to log data change as the amount of data grows?

Scenario Under Consideration

Analyze the time complexity of the following data logging code snippet.

import time

def log_data(sensor_readings):
    with open('data_log.txt', 'a') as file:
        for reading in sensor_readings:
            file.write(f"{reading}\n")
            time.sleep(0.01)  # simulate delay

# sensor_readings is a list of values

This code appends each sensor reading to a file one by one, simulating a small delay for each write.

Identify Repeating Operations

Look at what repeats as input grows.

• Primary operation: Loop over each sensor reading to write it to the file.
• How many times: Once for each reading in the input list.

How Execution Grows With Input

As the number of readings increases, the time to log grows proportionally.

Input Size (n)	Approx. Operations
10	10 writes and delays
100	100 writes and delays
1000	1000 writes and delays

Pattern observation: Doubling the readings roughly doubles the time taken.

Final Time Complexity

Time Complexity: O(n)

This means the time to log data grows directly with the number of readings.

Common Mistake

[X] Wrong: "Writing to a file once means logging many readings is always fast."

[OK] Correct: Each reading is written separately, so more readings mean more writes and more time.

Interview Connect

Understanding how data logging time grows helps you design efficient IoT systems and shows you can think about real-world resource use.

Self-Check

"What if we buffered all readings and wrote them to the file in one go? How would the time complexity change?"

Practice

1. Why is data logging important for IoT devices like Raspberry Pi sensors?

easy

A. It automatically updates the device software.

B. It makes the device run faster instantly.

C. It reduces the power consumption of the device.

D. It helps track device activity and detect problems over time.

Solution

1. Step 1: Understand the purpose of data logging

   Data logging records information from devices continuously or at intervals.

2. Step 2: Identify benefits for IoT devices

   This recorded data helps track device activity and find issues over time.

3. Final Answer:

   It helps track device activity and detect problems over time. -> Option D

4. Quick Check:

   Data logging = track and detect problems [OK]

Hint: Data logging = tracking device info over time [OK]

Common Mistakes:

• Confusing logging with speeding up device
• Thinking logging reduces power use
• Assuming logging updates software automatically

2. Which command correctly appends sensor data to a log file on Raspberry Pi?

easy

A. echo "temp=25" >> sensor.log

B. echo "temp=25" > sensor.log

C. cat sensor.log >> echo "temp=25"

D. echo "temp=25" | sensor.log

Solution

1. Step 1: Understand shell redirection operators

   '>>' appends text to a file, '>' overwrites the file.

2. Step 2: Choose the command that appends data

   Only 'echo "temp=25" >> sensor.log' appends without erasing existing data.

3. Final Answer:

   echo "temp=25" >> sensor.log -> Option A

4. Quick Check:

   Append with >> operator [OK]

Hint: Use >> to add data without erasing file [OK]

Common Mistakes:

• Using > which overwrites the file
• Misusing cat or pipe commands incorrectly
• Confusing append and overwrite operators

3. Given this Python code on Raspberry Pi, what will be the content of 'log.txt' after running it twice?

with open('log.txt', 'a') as f:
    f.write('Temperature: 22\n')

medium

A. Temperature: 22

B. Temperature: 22\n

C. Temperature: 22\nTemperature: 22\n

D. Error: file not found

Solution

1. Step 1: Understand file mode 'a' in Python

   Mode 'a' appends text to the file without deleting existing content.

2. Step 2: Analyze running code twice

   Each run adds 'Temperature: 22\n' once, so two runs add it twice.

3. Final Answer:

   Temperature: 22\nTemperature: 22\n -> Option C

4. Quick Check:

   Append mode adds lines each run [OK]

Hint: Mode 'a' appends, so repeated runs add lines [OK]

Common Mistakes:

• Thinking 'a' overwrites file
• Ignoring newline characters
• Expecting error when file exists

4. This Python code is meant to log sensor data but fails to save anything. What is the error?

f = open('data.log', 'w')
f.write('Humidity: 45%')
f.close()

medium

A. The file mode 'w' erases previous logs each run.

B. Missing newline character causes no data saved.

C. File is not closed properly.

D. The write method syntax is incorrect.

Solution

1. Step 1: Understand file mode 'w' behavior

   Mode 'w' overwrites the file, erasing previous logs each time.

2. Step 2: Identify why logs seem missing

   Each run deletes old data, so only last run's data remains, seeming like no logs.

3. Final Answer:

   The file mode 'w' erases previous logs each run. -> Option A

4. Quick Check:

   'w' mode overwrites file [OK]

Hint: Use 'a' mode to keep old logs, not 'w' [OK]

Common Mistakes:

• Thinking missing newline stops saving
• Assuming file not closed causes no save
• Believing write syntax is wrong

5. You want to log temperature and humidity every minute on a Raspberry Pi and keep logs for a week. Which approach best supports this goal?

hard

A. Overwrite a single log file every minute with new data only.

B. Use a Python script appending data to a daily log file and rotate files weekly.

C. Store data only in memory without saving to disk.

D. Log data once and delete logs after one hour.

Solution

1. Step 1: Understand logging frequency and retention needs

   Logging every minute generates many entries; keeping a week requires file management.

2. Step 2: Choose a method that appends and rotates logs

   Appending to daily files and rotating weekly keeps data organized and manageable.

3. Final Answer:

   Use a Python script appending data to a daily log file and rotate files weekly. -> Option B

4. Quick Check:

   Append + rotate files = best for long-term logs [OK]

Hint: Append data daily and rotate files weekly [OK]

Common Mistakes:

• Overwriting logs loses past data
• Not saving data to disk risks loss
• Deleting logs too soon loses history