MSET and MGET for bulk operations in Redis - Time & Space Complexity

Time Complexity: MSET and MGET for bulk operations

O(n)

Understanding Time Complexity

When using Redis commands like MSET and MGET, it's important to know how the time to run them changes as you add more keys.

We want to understand how the work grows when setting or getting many keys at once.

Scenario Under Consideration

Analyze the time complexity of the following Redis commands.

# Set multiple keys and values at once
MSET key1 value1 key2 value2 key3 value3 ... keyN valueN

# Get multiple keys at once
MGET key1 key2 key3 ... keyN
    

These commands set or get many keys in one call instead of one by one.

Identify Repeating Operations

Look at what repeats inside these commands.

• Primary operation: Processing each key-value pair for MSET, or each key for MGET.
• How many times: Once per key (N times for N keys).

How Execution Grows With Input

As you add more keys, the work grows in a simple way.

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

Pattern observation: The work grows evenly as you add more keys, roughly one step per key.

Final Time Complexity

Time Complexity: O(n)

This means the time to run MSET or MGET grows directly with the number of keys you use.

Common Mistake

[X] Wrong: "MSET and MGET run in constant time no matter how many keys are involved."

[OK] Correct: Each key still needs to be processed, so more keys mean more work and more time.

Interview Connect

Understanding how bulk commands scale helps you write efficient Redis code and explain your choices clearly in conversations.

Self-Check

"What if we used multiple separate SET or GET commands instead of MSET or MGET? How would the time complexity change?"

Practice

1.

What does the Redis command MSET do?

easy

A. Increments multiple numeric keys

B. Stores multiple key-value pairs in one command

C. Deletes multiple keys at once

D. Retrieves multiple values for given keys

Solution

1. Step 1: Understand MSET purpose

   The MSET command is used to save many keys and their values in one go, making it efficient for bulk storage.

2. Step 2: Compare with other commands

   MGET retrieves values, DEL deletes keys, and INCR increments numeric keys, so these are not what MSET does.

3. Final Answer:

   Stores multiple key-value pairs in one command -> Option B

4. Quick Check:

   MSET stores many keys at once = D [OK]

Hint: MSET saves many keys and values together [OK]

Common Mistakes:

• Confusing MSET with MGET
• Thinking MSET deletes keys
• Assuming MSET increments values

2.

Which of the following is the correct syntax to set multiple keys key1 and key2 with values val1 and val2 using MSET?

?

easy

A. MSET {key1: val1, key2: val2}

B. MSET (key1, val1), (key2, val2)

C. MSET key1 val1 key2 val2

D. MSET [key1, val1, key2, val2]

Solution

1. Step 1: Recall MSET syntax

   The correct syntax for MSET is to list keys and values in sequence separated by spaces: MSET key1 val1 key2 val2.

2. Step 2: Identify incorrect formats

   Parentheses, braces, or brackets are not used in Redis commands for MSET. So options B, C, and D are invalid syntax.

3. Final Answer:

   MSET key1 val1 key2 val2 -> Option C

4. Quick Check:

   MSET uses space-separated key value pairs = A [OK]

Hint: MSET uses space-separated key value pairs [OK]

Common Mistakes:

• Using parentheses or braces in command
• Separating pairs with commas
• Trying to pass a dictionary or list

3.

Given the commands below, what will be the output of the MGET command?

MSET name Alice age 30 city Paris
MGET name age city

medium

A. ["Alice", "30", "Paris"]

B. ["name", "age", "city"]

C. ["Alice", 30, "Paris"]

D. ["Alice", null, "Paris"]

Solution

1. Step 1: Understand MSET effect

   The MSET command sets keys name, age, and city with values "Alice", "30", and "Paris" respectively as strings.

2. Step 2: Predict MGET output

   MGET name age city returns the values for these keys in order as strings: ["Alice", "30", "Paris"].

3. Final Answer:

   ["Alice", "30", "Paris"] -> Option A

4. Quick Check:

   MGET returns values in order = B [OK]

Hint: MGET returns values as strings in key order [OK]

Common Mistakes:

• Expecting numeric 30 instead of string "30"
• Confusing keys with values in output
• Assuming missing keys return null

4.

What is wrong with this Redis command sequence?

MSET key1 val1 key2
MGET key1 key2

medium

A. MSET is missing a value for key2, causing an error

B. MGET syntax is incorrect, keys must be comma-separated

C. MSET keys must be quoted strings

D. MGET cannot retrieve multiple keys

Solution

1. Step 1: Check MSET command completeness

   The MSET command requires pairs of keys and values. Here, key2 has no value, so the command is incomplete and causes an error.

2. Step 2: Verify MGET syntax

   MGET accepts space-separated keys, so the syntax is correct. Quoting keys is not required in Redis commands.

3. Final Answer:

   MSET is missing a value for key2, causing an error -> Option A

4. Quick Check:

   MSET needs key-value pairs = A [OK]

Hint: MSET needs pairs: key then value [OK]

Common Mistakes:

• Leaving out a value for a key in MSET
• Using commas in MGET keys
• Quoting keys unnecessarily

5.

You want to store user data for three users with keys user:1, user:2, and user:3 and their names Alice, Bob, and Carol. Which command correctly sets all three users at once and then fetches their names?

hard

A. SET user:1 Alice
SET user:2 Bob
SET user:3 Carol
GET user:1 user:2 user:3

B. MSET {user:1: Alice, user:2: Bob, user:3: Carol}
MGET [user:1, user:2, user:3]

C. MSET user:1=Alice user:2=Bob user:3=Carol
MGET user:1 user:2 user:3

D. MSET user:1 Alice user:2 Bob user:3 Carol
MGET user:1 user:2 user:3

Solution

1. Step 1: Use correct MSET syntax for multiple keys

   The MSET command requires keys and values listed in sequence separated by spaces, like MSET user:1 Alice user:2 Bob user:3 Carol.

2. Step 2: Use MGET with space-separated keys

   MGET fetches values for multiple keys separated by spaces, so MGET user:1 user:2 user:3 is correct.

3. Step 3: Identify incorrect options

   Options B and D use invalid syntax with braces or equals signs. SET user:1 Alice SET user:2 Bob SET user:3 Carol GET user:1 user:2 user:3 uses multiple SET commands and an invalid GET with multiple keys, which is not supported.

4. Final Answer:

   MSET user:1 Alice user:2 Bob user:3 Carol MGET user:1 user:2 user:3 -> Option D

5. Quick Check:

   MSET and MGET use space-separated keys and values = C [OK]

Hint: MSET and MGET use space-separated keys and values [OK]

Common Mistakes:

• Using braces or equals signs in MSET
• Trying to GET multiple keys at once
• Using multiple SET commands instead of MSET