InfluxDB for time-series data in Raspberry Pi - Time & Space Complexity

Time Complexity: InfluxDB for time-series data

O(n)

Understanding Time Complexity

When working with InfluxDB on a Raspberry Pi, it's important to understand how the time it takes to store and query data grows as you add more time-series entries.

We want to know how the number of operations changes when the amount of data increases.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

from influxdb_client import InfluxDBClient

client = InfluxDBClient(url="http://localhost:8086", token="my-token", org="my-org")
query_api = client.query_api()

query = 'from(bucket:"sensor_data") |> range(start: -1h) |> filter(fn: (r) => r._measurement == "temperature")'
result = query_api.query(org="my-org", query=query)

for table in result:
    for record in table.records:
        print(record.get_value())

This code queries temperature data from the last hour and prints each value.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through all records returned by the query.
• How many times: Once for each data point in the last hour matching the filter.

How Execution Grows With Input

As the number of temperature records in the last hour grows, the number of print operations grows the same way.

Input Size (n)	Approx. Operations
10	10 print operations
100	100 print operations
1000	1000 print operations

Pattern observation: The number of operations grows directly with the number of data points.

Final Time Complexity

Time Complexity: O(n)

This means the time to process and print data grows in a straight line with the number of records.

Common Mistake

[X] Wrong: "Querying InfluxDB always takes the same time no matter how much data there is."

[OK] Correct: The query time depends on how many records match and are returned; more data means more processing time.

Interview Connect

Understanding how data size affects query time in databases like InfluxDB shows you can reason about performance in real projects, a valuable skill for any developer.

Self-Check

"What if we added an index on the _measurement field? How would the time complexity of the query change?"

Practice

1. What is the main purpose of InfluxDB when used with a Raspberry Pi?

easy

A. To run a web server for hosting websites

B. To control GPIO pins directly

C. To compile Python programs

D. To store and manage time-series data like sensor readings

Solution

1. Step 1: Understand InfluxDB's role

   InfluxDB is designed to store time-series data, which means data points collected over time, such as sensor readings.

2. Step 2: Compare with other options

   Running a web server, compiling Python, or controlling GPIO pins are not the main functions of InfluxDB.

3. Final Answer:

   To store and manage time-series data like sensor readings -> Option D

4. Quick Check:

   InfluxDB = time-series data storage [OK]

Hint: InfluxDB is for time-stamped data storage [OK]

Common Mistakes:

• Confusing InfluxDB with web servers
• Thinking InfluxDB compiles code
• Assuming InfluxDB controls hardware pins

2. Which Python code snippet correctly writes a data point to InfluxDB on a Raspberry Pi?

easy

A. client.write_point('temperature', tags={'room':'kitchen'}, fields={'value':22.5})

B. client.write_points([{'measurement':'temperature','tags':{'room':'kitchen'},'fields':{'value':22.5}}])

C. client.write('temperature', {'room':'kitchen'}, 22.5)

D. client.insert_point('temperature', {'room':'kitchen'}, {'value':22.5})

Solution

1. Step 1: Recall correct method name and parameters

   The InfluxDB Python client uses the method write_points to write data points, and it expects a list of dictionaries with keys 'measurement', 'tags', and 'fields'.

2. Step 2: Check each option

   client.write_points([{'measurement':'temperature','tags':{'room':'kitchen'},'fields':{'value':22.5}}]) matches the correct method and data structure. Options B, C, and D use incorrect method names or parameter formats.

3. Final Answer:

   client.write_points([{'measurement':'temperature','tags':{'room':'kitchen'},'fields':{'value':22.5}}]) -> Option B

4. Quick Check:

   Use write_points with list of dicts [OK]

Hint: Use write_points with list of dicts for data [OK]

Common Mistakes:

• Using wrong method names like write_point or insert_point
• Passing dict instead of list of dicts
• Incorrect parameter structure

3. Given this Python code on Raspberry Pi using InfluxDB client:

data = [{"measurement": "humidity", "tags": {"room": "bedroom"}, "fields": {"value": 45}}]
client.write_points(data)
result = client.query('SELECT * FROM humidity WHERE room = \'bedroom\'')
print(list(result.get_points()))

What will be the output?

medium

A. SyntaxError

B. []

C. [{'time': '...', 'room': 'bedroom', 'value': 45}]

D. None

Solution

1. Step 1: Understand data insertion

   The code writes one data point with measurement 'humidity', tag 'room'='bedroom', and field 'value'=45. This data is stored in InfluxDB.

2. Step 2: Query and print results

   The query selects all points from 'humidity' where 'room'='bedroom'. Since the data was just inserted, the query returns that point. Printing the list of points shows a list with one dictionary containing time, room, and value keys.

3. Final Answer:

   [{'time': '...', 'room': 'bedroom', 'value': 45}] -> Option C

4. Quick Check:

   Inserted data queried returns list with one point [OK]

Hint: Inserted points appear in query results as dicts [OK]

Common Mistakes:

• Expecting empty list if data was inserted
• Confusing syntax error with query result
• Assuming None is returned from query

4. This Python code snippet on Raspberry Pi tries to write data to InfluxDB but fails:

data = {'measurement': 'temperature', 'tags': {'room': 'office'}, 'fields': {'value': 21.0}}
client.write_points(data)

What is the error and how to fix it?

medium

A. Error: write_points expects a list of points; fix by wrapping data in a list

B. Error: 'fields' key missing; fix by adding 'fields' key

C. Error: 'measurement' must be a string; fix by converting to string

D. No error; code works fine

Solution

1. Step 1: Identify method parameter requirements

   The write_points method requires a list of data points, even if only one point is written.

2. Step 2: Analyze given code

   The code passes a single dictionary instead of a list containing that dictionary, causing an error.

3. Final Answer:

   Error: write_points expects a list of points; fix by wrapping data in a list -> Option A

4. Quick Check:

   write_points needs list of dicts [OK]

Hint: Always pass a list to write_points even for one point [OK]

Common Mistakes:

• Passing dict instead of list to write_points
• Missing 'fields' key in data point
• Assuming no error occurs

5. You want to store temperature readings from multiple rooms on a Raspberry Pi using InfluxDB. Which Python code correctly writes two points with tags and fields in one call?

hard

A. client.write_points([
{'measurement': 'temperature', 'tags': {'room': 'living'}, 'fields': {'value': 20}},
{'measurement': 'temperature', 'tags': {'room': 'bedroom'}, 'fields': {'value': 22}}
])

B. client.write_points({
'measurement': 'temperature', 'tags': {'room': ['living', 'bedroom']}, 'fields': {'value': [20, 22]}
})

C. client.write_points([
{'measurement': 'temperature', 'tags': {'room': 'living', 'bedroom'}, 'fields': {'value': 20, 22}}
])

D. client.write_points('temperature', tags={'room': ['living', 'bedroom']}, fields={'value': [20, 22]})

Solution

1. Step 1: Understand data structure for multiple points

   Each data point must be a dictionary with 'measurement', 'tags', and 'fields'. Multiple points are passed as a list of such dictionaries.

2. Step 2: Evaluate options

   client.write_points([ {'measurement': 'temperature', 'tags': {'room': 'living'}, 'fields': {'value': 20}}, {'measurement': 'temperature', 'tags': {'room': 'bedroom'}, 'fields': {'value': 22}} ]) correctly uses a list of two dictionaries, each with proper tags and fields. Options A, B, and C misuse data structures or method parameters.

3. Final Answer:

   client.write_points([ {'measurement': 'temperature', 'tags': {'room': 'living'}, 'fields': {'value': 20}}, {'measurement': 'temperature', 'tags': {'room': 'bedroom'}, 'fields': {'value': 22}} ]) -> Option A

4. Quick Check:

   List of dicts for multiple points [OK]

Hint: Send multiple points as list of dicts with tags and fields [OK]

Common Mistakes:

• Passing lists inside tags or fields instead of separate points
• Incorrect method parameters
• Combining tags incorrectly in one dict