Memory-efficient data structures in Redis

Introduction

Memory-efficient data structures help store data in Redis using less memory, making your database faster and cheaper to run.

When you have lots of small pieces of data to store, like user sessions or counters.

When you want to save memory on a server with limited resources.

When you need to handle many keys without slowing down Redis.

When you want to reduce the cost of cloud storage by using less memory.

When you want your Redis database to respond faster by using compact data formats.

Syntax

Redis

Use Redis commands that create or work with memory-efficient structures like hashes, sets, sorted sets, or bitmaps.

Example:
HSET myhash field1 value1
SADD myset member1
SETBIT mybitmap 10 1

Redis automatically uses memory-efficient encodings for small hashes and sets.

You can check the encoding of a key with the command: OBJECT ENCODING keyname

Examples

Stores user data in a hash, which is memory-efficient for small sets of fields.

Redis

HSET user:1000 name "Alice" age 30

Stores a set of online users efficiently.

Redis

SADD online_users user1 user2 user3

Uses a bitmap to store flags in a very compact way.

Redis

SETBIT user_flags 5 1

Sample Program

This example creates a small hash for user:1 and then checks its memory encoding.

Redis

HSET user:1 name "Bob" age 25
HSET user:1 city "Paris"
OBJECT ENCODING user:1

Important Notes

Small hashes and sets are stored as ziplists or intsets internally, which use less memory.

Avoid storing large values in hashes if you want to keep memory usage low.

Use bitmaps for boolean flags to save space compared to strings or hashes.

Summary

Memory-efficient data structures help save RAM and improve Redis speed.

Hashes, sets, and bitmaps are common memory-saving structures in Redis.

Redis automatically optimizes small data sets to use less memory.

Practice

1. Which Redis data structure is best suited for storing many small key-value pairs efficiently in memory?

easy

A. List

B. Set

C. Hash

D. String

Solution

1. Step 1: Understand Redis data structures

   Hashes store multiple field-value pairs under one key, saving memory compared to many separate keys.

2. Step 2: Compare with other structures

   Lists and sets store collections but are less memory-efficient for many small pairs; strings store single values only.

3. Final Answer:

   Hash -> Option C

4. Quick Check:

   Hashes = memory-efficient key-value pairs [OK]

Hint: Use hashes for many small key-value pairs to save memory [OK]

Common Mistakes:

• Choosing List or Set for key-value pairs
• Thinking String can store multiple pairs
• Ignoring memory efficiency of Hashes

2. Which of the following is the correct Redis command to add a field-value pair to a hash named user:1?

easy

A. HSET user:1 name "Alice"

B. SADD user:1 name "Alice"

C. LPUSH user:1 name "Alice"

D. SET user:1 name "Alice"

Solution

1. Step 1: Identify the command for hashes

   HSET adds or updates a field in a hash key in Redis.

2. Step 2: Check other commands

   SADD is for sets, LPUSH for lists, SET for strings; none add fields to hashes.

3. Final Answer:

   HSET user:1 name "Alice" -> Option A

4. Quick Check:

   HSET = add field to hash [OK]

Hint: Use HSET to add fields to hashes in Redis [OK]

Common Mistakes:

• Using SADD or LPUSH for hashes
• Confusing SET with HSET
• Incorrect command syntax

3. Given the Redis commands:
HSET user:2 age 30
HSET user:2 city "NYC"
What will HGETALL user:2 return?

medium

A. ["age", "30", "city", "NYC"]

B. ["user:2", "age", "30", "city", "NYC"]

C. ["age", 30, "city", "NYC"]

D. ["age", "30", "city"]

Solution

1. Step 1: Understand HSET commands

   Two fields, 'age' and 'city', are set with values '30' and 'NYC' in hash 'user:2'.

2. Step 2: Check HGETALL output format

   HGETALL returns a flat list of field-value pairs as strings.

3. Final Answer:

   ["age", "30", "city", "NYC"] -> Option A

4. Quick Check:

   HGETALL returns field-value pairs list [OK]

Hint: HGETALL returns flat list of fields and values [OK]

Common Mistakes:

• Expecting key name in output
• Mixing data types (string vs integer)
• Missing value for a field

4. You run the command HSET user:3 name "Bob" but get an error. Which is the most likely cause?

medium

A. Redis does not support hashes with string fields

B. The key user:3 already holds a string value

C. HSET requires a numeric field value

D. The field name is reserved and cannot be used

Solution

1. Step 1: Understand Redis type errors

   If the key 'user:3' holds a string, trying to use HSET (hash command) causes a type error.

2. Step 2: Check other options

   Field names are not reserved, HSET accepts strings, and Redis supports string fields in hashes.

3. Final Answer:

   The key user:3 already holds a string value -> Option B

4. Quick Check:

   Type mismatch causes HSET error [OK]

Hint: Check key type before using hash commands [OK]

Common Mistakes:

• Assuming field names are restricted
• Thinking HSET needs numeric values
• Ignoring Redis data type rules

5. You want to store user preferences with many optional fields but minimize memory. Which Redis approach is best?

hard

A. Use a set with all field names as members

B. Use a list with all possible fields and empty strings for missing

C. Use separate string keys for each field

D. Use a hash with only fields that have values

Solution

1. Step 1: Consider memory efficiency

   Hashes store only existing fields, saving memory by omitting empty or missing fields.

2. Step 2: Evaluate other options

   Lists with empty strings waste memory; sets store unique members but not key-value pairs; separate keys increase overhead.

3. Final Answer:

   Use a hash with only fields that have values -> Option D

4. Quick Check:

   Hashes save memory by storing only present fields [OK]

Hint: Store only present fields in hashes to save memory [OK]

Common Mistakes:

• Using lists with empty placeholders
• Using sets for key-value data
• Creating many separate keys