HMSET and HMGET for bulk in Redis - Time & Space Complexity

Time Complexity: HMSET and HMGET for bulk

O(n)

Understanding Time Complexity

We want to understand how the time to store and retrieve many fields in Redis changes as the number of fields grows.

How does the work grow when using HMSET and HMGET with many fields at once?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

HMSET user:1000 name "Alice" age "30" city "Paris" country "France"
HMGET user:1000 name age city country
    

This code stores multiple fields for a user in one command and then retrieves those fields in one command.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Processing each field in the hash for setting or getting.
• How many times: Once for each field included in the HMSET or HMGET command.

How Execution Grows With Input

As you add more fields to set or get, the time to complete the command grows roughly in direct proportion to the number of fields.

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

Pattern observation: The work grows linearly as you add more fields.

Final Time Complexity

Time Complexity: O(n)

This means the time to set or get fields grows directly with the number of fields you include.

Common Mistake

[X] Wrong: "HMSET and HMGET always take constant time no matter how many fields."

[OK] Correct: Each field must be processed, so more fields mean more work and more time.

Interview Connect

Understanding how bulk commands scale helps you design efficient data access patterns and shows you can think about performance in real systems.

Self-Check

"What if we used multiple single-field HSET and HGET commands instead of one HMSET and HMGET? How would the time complexity change?"

Practice

1. What does the Redis command HMSET do?

easy

A. Retrieves all keys from the database.

B. Deletes a hash key and all its fields.

C. Stores multiple fields and their values in a single hash key at once.

D. Increments a numeric value in a hash field.

Solution

1. Step 1: Understand HMSET purpose

   The HMSET command is used to save many fields and their values inside one hash key in Redis.

2. Step 2: Compare with other commands

   Other commands like DEL delete keys, and INCR increments values, so they do not match HMSET's bulk saving role.

3. Final Answer:

   Stores multiple fields and their values in a single hash key at once. -> Option C

4. Quick Check:

   HMSET saves many fields at once = B [OK]

Hint: HMSET saves many fields in one hash key at once [OK]

Common Mistakes:

• Confusing HMSET with commands that delete keys
• Thinking HMSET retrieves data instead of saving
• Mixing HMSET with single field commands like HSET

2. Which of the following is the correct syntax to set multiple fields in a hash named user:1 using HMSET?

easy

A. HMSET user:1 ["name", "Alice", "age", 30, "city", "NY"]

B. HMSET user:1 (name, "Alice", age, 30, city, "NY")

C. HMSET user:1 {name: "Alice", age: 30, city: "NY"}

D. HMSET user:1 name "Alice" age 30 city "NY"

Solution

1. Step 1: Recall HMSET syntax

   HMSET expects the key followed by field and value pairs separated by spaces, without brackets or braces.

2. Step 2: Check each option

   HMSET user:1 name "Alice" age 30 city "NY" matches the correct syntax: key, field, value, field, value... Options B, C, and D use invalid brackets or JSON-like syntax not accepted by Redis.

3. Final Answer:

   HMSET user:1 name "Alice" age 30 city "NY" -> Option D

4. Quick Check:

   HMSET syntax is key + field value pairs space-separated = A [OK]

Hint: HMSET uses space-separated field-value pairs, no brackets [OK]

Common Mistakes:

• Using brackets or braces in HMSET command
• Putting fields and values inside parentheses
• Confusing HMSET with JSON syntax

3. Given the following commands executed in Redis:
HMSET product:100 name "Laptop" price 1200 stock 30
HMGET product:100 name price
What will be the output of the HMGET command?

medium

A. ["Laptop", "1200"]

B. ["Laptop", 1200]

C. ["name", "price"]

D. ["Laptop"]

Solution

1. Step 1: Understand HMSET stored data

   The HMSET command stores fields 'name' with value "Laptop" and 'price' with value "1200" (as string) in the hash 'product:100'.

2. Step 2: Understand HMGET output

   HMGET fetches the values of the requested fields in order, returning an array of strings: ["Laptop", "1200"].

3. Final Answer:

   ["Laptop", "1200"] -> Option A

4. Quick Check:

   HMGET returns values as strings in array = A [OK]

Hint: HMGET returns values as strings in array order [OK]

Common Mistakes:

• Expecting numeric types instead of strings
• Confusing HMGET output with field names
• Getting only one value instead of array

4. You run the command HMGET user:5 name age but get (nil) for both fields. What is the most likely reason?

medium

A. Redis server is down.

B. The hash key user:5 does not exist or has no such fields.

C. HMGET cannot fetch multiple fields at once.

D. HMGET syntax requires brackets around field names.

Solution

1. Step 1: Interpret (nil) results

   Getting (nil) means the requested fields or the hash key do not exist in Redis.

2. Step 2: Check command syntax and server status

   HMGET syntax is correct without brackets, and if the server was down, no response would be received.

3. Final Answer:

   The hash key user:5 does not exist or has no such fields. -> Option B

4. Quick Check:

   (nil) means missing key or fields = D [OK]

Hint: (nil) means key or fields missing, not syntax error [OK]

Common Mistakes:

• Adding brackets around fields in HMGET
• Assuming HMGET cannot fetch multiple fields
• Thinking server down causes (nil) responses

5. You want to store user profile data with fields name, email, and age in Redis using HMSET, then retrieve only email and age with HMGET. Which sequence of commands is correct?

hard

A. HMSET user:10 name "Bob" email "[e-mail]" age 25HMGET user:10 email age

B. HMSET user:10 {name: "Bob", email: "[e-mail]", age: 25}HMGET user:10 [email, age]

C. HMSET user:10 (name "Bob", email "[e-mail]", age 25)HMGET user:10 (email age)

D. HMSET user:10 name="Bob" email="[e-mail]" age=25HMGET user:10 email age

Solution

1. Step 1: Write correct HMSET command

   HMSET requires key followed by field-value pairs separated by spaces without brackets or equals signs, so HMSET user:10 name "Bob" email "[e-mail]" age 25
   HMGET user:10 email age is correct.

2. Step 2: Write correct HMGET command

   HMGET takes the key and list of fields separated by spaces, so HMSET user:10 name "Bob" email "[e-mail]" age 25
   HMGET user:10 email age's HMGET is correct.

3. Final Answer:

   HMSET user:10 name "Bob" email "[e-mail]" age 25
   HMGET user:10 email age -> Option A

4. Quick Check:

   HMSET and HMGET use space-separated fields and values = C [OK]

Hint: Use space-separated fields and values, no brackets or equals [OK]

Common Mistakes:

• Using JSON or bracket syntax in HMSET
• Adding parentheses around fields in HMGET
• Using equals signs in HMSET command