Persistence and performance trade-off in Redis

Introduction

Persistence saves your data safely on disk. Performance means how fast Redis works. Sometimes, saving data can slow Redis down. So, you balance between saving data and speed.

When you want to keep data safe even if Redis restarts or crashes.

When you need Redis to respond very fast and can accept some data loss.

When you want to decide how often Redis saves data to disk.

When you want to choose between different ways Redis saves data.

When you want to avoid slowdowns during heavy data saving.

Syntax

Redis

redis.conf settings example:
save 900 1
save 300 10
save 60 10000
appendonly yes
appendfsync everysec

save lines set how often Redis saves snapshots (RDB files).

appendonly enables AOF (Append Only File) persistence for better durability.

Examples

Save the DB if at least 1 key changed in 900 seconds (15 minutes).

Redis

save 900 1

Turn off AOF persistence for better speed but less durability.

Redis

appendonly no

Turn on AOF and save to disk after every write (slow but safest).

Redis

appendonly yes
appendfsync always

Turn on AOF and save every second (good balance of safety and speed).

Redis

appendonly yes
appendfsync everysec

Sample Program

This config saves a snapshot if 10 keys change in 5 minutes and also uses AOF with syncing every second. This balances data safety and performance.

Redis

# redis.conf example for balanced persistence
save 300 10
appendonly yes
appendfsync everysec

Important Notes

RDB snapshots are fast but can lose recent changes if Redis crashes.

AOF is slower but safer because it logs every write.

You can combine RDB and AOF for better balance.

Summary

Persistence protects your data but can slow Redis down.

RDB snapshots save data at intervals, AOF logs every write.

Choose settings based on how much data loss you can accept and how fast you want Redis.

Practice

1. Which Redis persistence method saves data at specific time intervals, balancing durability and performance?

easy

A. No persistence

B. AOF logging

C. RDB snapshots

D. In-memory only

Solution

1. Step 1: Understand Redis persistence options

   Redis offers RDB snapshots and AOF logging for persistence.

2. Step 2: Identify method saving data at intervals

   RDB snapshots save data periodically, while AOF logs every write.

3. Final Answer:

   RDB snapshots -> Option C

4. Quick Check:

   Persistence by snapshots = RDB snapshots [OK]

Hint: Snapshots save periodically, logs save every write [OK]

Common Mistakes:

• Confusing AOF with snapshots
• Thinking no persistence saves data
• Assuming in-memory is persistent

2. Which Redis configuration option enables Append Only File (AOF) persistence?

easy

A. appendonly yes

B. appendonly no

C. save 900 1

D. stop-writes-on-bgsave-error no

Solution

1. Step 1: Identify AOF enabling option

   The option to enable AOF is 'appendonly yes'.

2. Step 2: Differentiate from snapshot options

   'save 900 1' relates to RDB snapshots, not AOF.

3. Final Answer:

   appendonly yes -> Option A

4. Quick Check:

   Enable AOF = appendonly yes [OK]

Hint: Enable AOF with 'appendonly yes' in config [OK]

Common Mistakes:

• Using 'appendonly no' disables AOF
• Confusing 'save' with AOF setting
• Misreading unrelated config options

3. Given Redis configured with RDB snapshots every 60 seconds and AOF enabled with 'appendfsync everysec', what is the maximum data loss if Redis crashes?

medium

A. Up to 1 second of data loss

B. Up to 60 seconds of data loss

C. No data loss

D. Up to 5 minutes of data loss

Solution

1. Step 1: Understand RDB snapshot interval

   Snapshots save every 60 seconds, so up to 60 seconds loss if using RDB only.

2. Step 2: Consider AOF 'appendfsync everysec'

   This setting syncs AOF every second, limiting loss to up to 1 second.

3. Step 3: Combine effects

   With both RDB and AOF enabled, Redis prioritizes AOF for recovery of recent writes, so maximum data loss is 1 second.

4. Final Answer:

   Up to 1 second of data loss -> Option A

5. Quick Check:

   AOF everysec = up to 1s loss [OK]

Hint: Max loss = AOF fsync interval when AOF enabled [OK]

Common Mistakes:

• Thinking RDB interval dominates with AOF enabled
• Ignoring AOF sync policy
• Confusing 'everysec' with immediate sync

4. You configured Redis with 'appendonly yes' but notice no AOF file is created. What is the most likely cause?

medium

A. AOF file is corrupted

B. RDB snapshots disabled

C. Disk is full

D. Redis was not restarted after config change

Solution

1. Step 1: Check if config changes take effect immediately

   Changing 'appendonly yes' requires Redis restart to activate.

2. Step 2: Rule out other causes

   Disk full or corruption would cause errors, snapshots don't affect AOF creation.

3. Final Answer:

   Redis was not restarted after config change -> Option D

4. Quick Check:

   Config changes need restart [OK]

Hint: Restart Redis after enabling AOF [OK]

Common Mistakes:

• Assuming snapshots affect AOF file
• Ignoring need to restart Redis
• Blaming disk issues without checking

5. You want Redis to minimize data loss but can tolerate some performance cost. Which configuration best fits this need?

hard

A. Enable RDB snapshots every 15 minutes and disable AOF

B. Enable AOF with 'appendfsync everysec' and RDB snapshots every 5 minutes

C. Enable AOF with 'appendfsync always' and disable RDB snapshots

D. Disable both AOF and RDB snapshots for max speed

Solution

1. Step 1: Understand data loss vs performance trade-off

   'appendfsync always' is safest but slowest; 'everysec' balances safety and speed.

2. Step 2: Combine AOF and snapshots for better durability

   Using both reduces data loss and improves recovery options.

3. Step 3: Evaluate options

   Enable AOF with 'appendfsync everysec' and RDB snapshots every 5 minutes balances minimal data loss with acceptable performance cost.

4. Final Answer:

   Enable AOF with 'appendfsync everysec' and RDB snapshots every 5 minutes -> Option B

5. Quick Check:

   Balanced persistence = AOF everysec + snapshots [OK]

Hint: Use AOF everysec plus snapshots for balance [OK]

Common Mistakes:

• Choosing 'appendfsync always' for performance
• Disabling persistence for safety
• Relying on snapshots alone for minimal loss