Redis with Python (redis-py) - Time & Space Complexity

Time Complexity: Redis with Python (redis-py)

O(n)

Understanding Time Complexity

When using Redis commands through Python, it's important to understand how the time to run commands changes as the data grows.

We want to know how the number of operations grows when we run common Redis commands with redis-py.

Scenario Under Consideration

Analyze the time complexity of the following Python code using redis-py.

import redis

r = redis.Redis()

# Add 1000 items to a Redis list
for i in range(1000):
    r.lpush('mylist', i)

# Retrieve all items
items = r.lrange('mylist', 0, -1)

This code pushes 1000 items to a Redis list and then retrieves all items from that list.

Identify Repeating Operations

Look for repeated actions that affect time.

• Primary operation: The loop calls lpush 1000 times to add items.
• How many times: 1000 times for adding, then one lrange to get all items.

How Execution Grows With Input

As the number of items increases, the time to add and retrieve grows.

Input Size (n)	Approx. Operations
10	~10 calls to lpush, 1 call to lrange returning 10 items
100	~100 calls to lpush, 1 call to lrange returning 100 items
1000	~1000 calls to lpush, 1 call to lrange returning 1000 items

Pattern observation: The number of lpush calls grows linearly with input size, and retrieving all items also grows linearly with the list size.

Final Time Complexity

Time Complexity: O(n)

This means the time to add and retrieve items grows in direct proportion to the number of items.

Common Mistake

[X] Wrong: "Adding items with lpush is always constant time regardless of list size."

[OK] Correct: While lpush is generally fast and operates in O(1) time per call, calling it many times adds up linearly, so total time grows with the number of items added.

Interview Connect

Understanding how Redis commands scale with data size helps you explain your choices clearly and shows you know how to handle real data growth.

Self-Check

"What if we used rpush instead of lpush? How would the time complexity change?"

Practice

1. What does the set() method do in redis-py?

easy

A. Lists all keys stored in Redis

B. Retrieves a value by key from Redis

C. Deletes a key from Redis

D. Stores a value with a specified key in Redis

Solution

1. Step 1: Understand the purpose of set()

   The set() method is used to save data in Redis by associating a value with a key.

2. Step 2: Compare with other methods

   get() retrieves data, delete() removes keys, and keys() lists keys, so they do not store data.

3. Final Answer:

   Stores a value with a specified key in Redis -> Option D

4. Quick Check:

   set() means store data [OK]

Hint: Remember: set = save data, get = retrieve data [OK]

Common Mistakes:

• Confusing set() with get()
• Thinking set() deletes keys
• Assuming set() lists keys

2. Which of the following is the correct syntax to get a value for key 'name' using redis-py?

easy

A. r.get('name')

B. r.get(name)

C. r.get['name']

D. r.get{name}

Solution

1. Step 1: Identify correct method call syntax

   In Python, method calls use parentheses with arguments inside, so r.get('name') is correct.

2. Step 2: Check argument format

   The key must be a string, so it needs quotes. Options A, B, and D have syntax errors or missing quotes.

3. Final Answer:

   r.get('name') -> Option A

4. Quick Check:

   Method call with parentheses and string key [OK]

Hint: Use parentheses and quotes for string keys in method calls [OK]

Common Mistakes:

• Omitting quotes around string keys
• Using square brackets instead of parentheses
• Using curly braces instead of parentheses

3. What will be the output of this code snippet?

import redis
r = redis.Redis()
r.set('color', 'blue')
value = r.get('color')
print(value)

medium

A. blue

B. b'blue'

C. None

D. Error

Solution

1. Step 1: Understand Redis returns bytes

   The get() method returns the value as bytes, so value is b'blue'.

2. Step 2: Print output

   Printing value shows the bytes literal b'blue', not the decoded string.

3. Final Answer:

   b'blue' -> Option B

4. Quick Check:

   Redis returns bytes, so output shows b'...' [OK]

Hint: Remember: Redis get returns bytes, not decoded string [OK]

Common Mistakes:

• Expecting a plain string without decoding
• Assuming None if key exists
• Thinking code raises error

4. Identify the error in this code snippet:

import redis
r = redis.Redis()
r.set('age', 30)
age = r.get('age')
print(age)

medium

A. get() returns bytes, need decoding

B. Cannot store integer directly with set()

C. Missing Redis server connection parameters

D. Syntax error in print statement

Solution

1. Step 1: Check data storage

   Redis-py converts integers to strings automatically, so storing 30 is valid.

2. Step 2: Check retrieval and printing

   get() returns bytes, so printing age shows bytes, not a readable string or integer. Decoding is needed.

3. Final Answer:

   get() returns bytes, need decoding -> Option A

4. Quick Check:

   Decode bytes after get() to read value [OK]

Hint: Always decode bytes from get() before printing [OK]

Common Mistakes:

• Thinking set() rejects integers
• Ignoring bytes return type from get()
• Assuming print syntax error

5. You want to store user info as a dictionary in Redis using redis-py. Which approach correctly saves and retrieves the dictionary?

hard

A. Store dictionary as string with set() and retrieve with get() without decoding

B. Directly use set() with the dictionary and get() to retrieve

C. Use set() with json.dumps() to save and json.loads() after get()

D. Use hmset() to save and hgetall() to retrieve

Solution

1. Step 1: Understand Redis stores strings/bytes

   Redis cannot store Python dicts directly; they must be converted to strings.

2. Step 2: Use JSON to serialize and deserialize

   Using json.dumps() converts dict to string for set(), and json.loads() converts back after get().

3. Step 3: Evaluate other options

   hmset() is deprecated; direct dict storage fails; storing string without decoding causes errors.

4. Final Answer:

   Use set() with json.dumps() and json.loads() after get() -> Option C

5. Quick Check:

   Serialize dict to string before storing, deserialize after retrieval [OK]

Hint: Serialize dict with JSON before set(), deserialize after get() [OK]

Common Mistakes:

• Trying to store dict directly
• Using deprecated hmset() method
• Not decoding bytes before json.loads()