Why key management matters in Redis - Performance Analysis

Time Complexity: Why key management matters

O(n)

Understanding Time Complexity

When working with Redis, how you manage keys affects how fast your commands run.

We want to see how the number of keys impacts the time it takes to do operations.

Scenario Under Consideration

Analyze the time complexity of deleting multiple keys using the DEL command.

# Delete multiple keys at once
DEL key1 key2 key3 ... keyN

# Or delete keys matching a pattern
EVAL "return redis.call('DEL', unpack(redis.call('KEYS', ARGV[1])))" 0 pattern*
    

This code deletes a list of keys or all keys matching a pattern.

Identify Repeating Operations

Look for repeated steps that take time as input grows.

• Primary operation: Deleting each key one by one.
• How many times: Once for each key to delete.

How Execution Grows With Input

As you delete more keys, the time grows with the number of keys.

Input Size (n)	Approx. Operations
10	10 delete steps
100	100 delete steps
1000	1000 delete steps

Pattern observation: The time grows directly with how many keys you delete.

Final Time Complexity

Time Complexity: O(n)

This means if you delete twice as many keys, it takes about twice as long.

Common Mistake

[X] Wrong: "Deleting many keys is always instant because Redis is fast."

[OK] Correct: Even though Redis is fast, deleting more keys takes more time because each key must be removed.

Interview Connect

Understanding how key count affects command time helps you write better Redis commands and avoid slowdowns.

Self-Check

"What if we used SCAN instead of KEYS to find keys before deleting? How would the time complexity change?"

Practice

1. Why is it important to use clear and consistent key names in Redis?

easy

A. It helps organize data and makes it easier to find keys.

B. It increases the size of the Redis database automatically.

C. It allows Redis to run without any memory limits.

D. It prevents Redis from accepting new connections.

Solution

1. Step 1: Understand key naming purpose

   Clear and consistent key names help keep data organized in Redis.

2. Step 2: Identify benefits of good key names

   Organized keys make it easier to find and manage data quickly.

3. Final Answer:

   It helps organize data and makes it easier to find keys. -> Option A

4. Quick Check:

   Good key names = easier data management [OK]

Hint: Think: clear names = easy to find data [OK]

Common Mistakes:

• Assuming key names affect database size
• Believing key names control memory limits
• Confusing key names with connection settings

2. Which of the following is the correct way to set a key with a prefix in Redis CLI?

easy

A. SET user-1001 "John"

B. SET user:1001 "John"

C. SET user/1001 "John"

D. SET user1001 "John"

Solution

1. Step 1: Recognize common prefix pattern

   Using a colon ':' is the standard way to separate prefixes in Redis keys.

2. Step 2: Check each option's syntax

   Only SET user:1001 "John" uses the colon prefix format correctly.

3. Final Answer:

   SET user:1001 "John" -> Option B

4. Quick Check:

   Prefix with ':' is correct Redis key style [OK]

Hint: Use ':' to separate prefixes in keys [OK]

Common Mistakes:

• Using dashes or slashes instead of colons
• Not using any separator between prefix and key
• Confusing key naming with command syntax

3. Given these Redis keys: user:1, user:2, order:1, what will the command KEYS user:* return?

medium

A. []

B. ["order:1"]

C. ["user:1", "user:2", "order:1"]

D. ["user:1", "user:2"]

Solution

1. Step 1: Understand the KEYS command with pattern

   KEYS user:* matches all keys starting with 'user:' prefix.

2. Step 2: Identify matching keys

   Only 'user:1' and 'user:2' match the pattern; 'order:1' does not.

3. Final Answer:

   ["user:1", "user:2"] -> Option D

4. Quick Check:

   KEYS user:* returns keys with 'user:' prefix [OK]

Hint: KEYS with prefix* returns keys starting with prefix [OK]

Common Mistakes:

• Expecting keys with different prefixes to appear
• Thinking KEYS returns empty if any key exists
• Confusing pattern matching syntax

4. You want to delete all keys with prefix session: but your command DEL session:* returns an error. What is the problem?

medium

A. DEL command requires a password to delete keys.

B. The prefix 'session:' is invalid in Redis keys.

C. DEL does not accept wildcards; you must delete keys individually.

D. You must restart Redis before deleting keys.

Solution

1. Step 1: Understand DEL command behavior

   DEL command deletes specific keys; it does not support wildcards.

2. Step 2: Identify correct deletion method

   To delete keys by pattern, you must first find keys (e.g., with KEYS) then delete them individually.

3. Final Answer:

   DEL does not accept wildcards; you must delete keys individually. -> Option C

4. Quick Check:

   DEL needs exact keys, no wildcards [OK]

Hint: DEL needs exact keys; use KEYS + DEL loop [OK]

Common Mistakes:

• Trying to use wildcards directly with DEL
• Thinking prefixes are invalid keys
• Believing Redis needs restart to delete keys

5. You have keys cache:item:1, cache:item:2, and cache:user:1. You want to delete only keys related to items efficiently. Which approach is best?

hard

A. Use SCAN 0 MATCH cache:item:* to find keys, then delete them one by one.

B. Run DEL cache:* to delete all cache keys at once.

C. Rename keys to remove 'item' prefix before deleting.

D. Flush the entire Redis database to remove all keys.

Solution

1. Step 1: Identify keys to delete

   Only keys with prefix 'cache:item:' should be deleted, not 'cache:user:'.

2. Step 2: Choose efficient deletion method

   SCAN with MATCH finds keys without blocking Redis; then delete keys individually.

3. Step 3: Avoid unsafe commands

   DEL with wildcards or FLUSHDB deletes too much; renaming keys is unnecessary.

4. Final Answer:

   Use SCAN 0 MATCH cache:item:* to find keys, then delete them one by one. -> Option A

5. Quick Check:

   SCAN + MATCH + DEL = safe selective deletion [OK]

Hint: Use SCAN with MATCH to safely find keys before deleting [OK]

Common Mistakes:

• Using DEL with wildcards causing errors
• Flushing entire DB losing all data
• Renaming keys unnecessarily before deletion