RDB vs AOF comparison in Redis - Performance Comparison

Time Complexity: RDB vs AOF comparison

O(n)

Understanding Time Complexity

When saving data in Redis, two main methods are used: RDB and AOF. Each method takes time to save data, and this time changes as the data grows.

We want to understand how the time to save data grows with the amount of data for both methods.

Scenario Under Consideration

Analyze the time complexity of saving data using RDB snapshot and AOF append-only file.

# RDB snapshot
SAVE

# AOF append
APPENDONLY yes
# Commands are appended as they happen
SET key value
INCR counter
DEL key

RDB saves the whole dataset at once. AOF saves each command as it happens.

Identify Repeating Operations

Look at what repeats when saving data.

• Primary operation for RDB: Writing the entire dataset to disk in one go.
• How many times: Once per snapshot, but the work depends on dataset size.
• Primary operation for AOF: Appending each command to the file as it happens.
• How many times: Once per command, so many times as commands run.

How Execution Grows With Input

How does saving time grow as data grows?

Input Size (n)	RDB Approx. Operations	AOF Approx. Operations
10 keys	Write 10 keys at once	Append 10 commands one by one
100 keys	Write 100 keys at once	Append 100 commands one by one
1000 keys	Write 1000 keys at once	Append 1000 commands one by one

RDB time grows with total data size because it writes all at once. AOF time grows with number of commands because it writes each command separately.

Final Time Complexity

Time Complexity: O(n) for both, but with different meanings.

RDB time grows linearly with dataset size when saving snapshots. AOF time grows linearly with number of commands appended.

Common Mistake

[X] Wrong: "RDB is always faster because it saves less often."

[OK] Correct: RDB writes the whole dataset at once, which can take longer if data is large. AOF writes smaller pieces more often, so total time depends on command volume.

Interview Connect

Understanding how Redis saves data helps you explain trade-offs in real systems. It shows you can think about how work grows with data, a key skill in many jobs.

Self-Check

"What if AOF was rewritten less often, batching commands? How would that affect time complexity?"

Practice

1. Which Redis persistence method saves the entire dataset at specific time intervals?

easy

A. AOF (Append Only File)

B. RDB (Redis Database snapshot)

C. Both RDB and AOF save snapshots

D. Neither RDB nor AOF save snapshots

Solution

1. Step 1: Understand RDB persistence

   RDB saves the dataset by creating snapshots at set intervals.

2. Step 2: Compare with AOF

   AOF logs every write operation, not snapshots.

3. Final Answer:

   RDB (Redis Database snapshot) -> Option B

4. Quick Check:

   Snapshot saving = RDB [OK]

Hint: RDB = snapshots at intervals, AOF = logs every change [OK]

Common Mistakes:

• Confusing AOF with snapshot saving
• Thinking both save snapshots
• Believing neither saves snapshots

2. Which of the following is the correct Redis command to enable AOF persistence?

easy

A. CONFIG SET appendonly yes

B. CONFIG SET save "900 1 300 10 60 10000"

C. CONFIG SET rdbcompression no

D. CONFIG SET maxmemory-policy allkeys-lru

Solution

1. Step 1: Identify AOF enabling command

   The command to enable AOF is CONFIG SET appendonly yes.

2. Step 2: Check other options

   CONFIG SET save "900 1 300 10 60 10000" sets RDB save intervals, C disables RDB compression, D sets memory eviction policy.

3. Final Answer:

   CONFIG SET appendonly yes -> Option A

4. Quick Check:

   Enable AOF = appendonly yes [OK]

Hint: Enable AOF with 'appendonly yes' command [OK]

Common Mistakes:

• Confusing RDB save command with AOF
• Using unrelated config commands
• Forgetting to set appendonly to yes

3. Given Redis configured with AOF enabled and fsync set to 'everysec', what is the expected data durability behavior?

medium

A. Data is saved only at intervals, risking data loss of last seconds

B. Every write is immediately saved to disk, no data loss

C. Data is never saved to disk automatically

D. Data is saved only when Redis restarts

Solution

1. Step 1: Understand AOF with fsync everysec

   With fsync set to 'everysec', Redis writes AOF data to disk every second.

2. Step 2: Analyze durability implications

   This means data could be lost if Redis crashes within the last second before fsync.

3. Final Answer:

   Data is saved only at intervals, risking data loss of last seconds -> Option A

4. Quick Check:

   AOF everysec fsync = possible 1-second data loss [OK]

Hint: AOF everysec fsync means possible 1-second data loss [OK]

Common Mistakes:

• Assuming every write is immediately saved
• Thinking data is never saved automatically
• Confusing with no persistence

4. You enabled both RDB and AOF persistence in Redis, but after a crash, data is missing. What is the most likely cause?

medium

A. Redis does not support using both RDB and AOF together

B. Redis was not restarted after enabling persistence

C. RDB snapshot interval is too long, losing recent changes

D. AOF file is corrupted and Redis cannot load it

Solution

1. Step 1: Understand RDB and AOF coexistence

   Redis supports both RDB and AOF, preferring to load AOF first on restart if available.

2. Step 2: Analyze data loss causes

   With both enabled, if data is missing after a crash, the most likely cause is AOF corruption, causing fallback to the older RDB snapshot and loss of recent changes.

3. Final Answer:

   AOF file is corrupted and Redis cannot load it -> Option D

4. Quick Check:

   Data loss with both = AOF corrupted [OK]

Hint: With both enabled, data loss likely from AOF corruption [OK]

Common Mistakes:

• Believing Redis can't use both persistences
• Thinking RDB interval too long is the cause
• Forgetting to restart Redis

5. You want Redis to recover data quickly after a crash but can tolerate losing up to 1 minute of recent writes. Which persistence setup is best?

hard

A. Enable AOF with fsync always, disable RDB

B. Enable both RDB and AOF with fsync everysec

C. Enable RDB snapshots every 60 seconds, disable AOF

D. Disable both RDB and AOF for fastest performance

Solution

1. Step 1: Match recovery speed and data loss tolerance

   RDB snapshots every 60 seconds allow fast recovery but may lose up to 1 minute of data.

2. Step 2: Compare with AOF options

   AOF with fsync always is slower but safer; both enabled adds overhead; disabling persistence risks total data loss.

3. Final Answer:

   Enable RDB snapshots every 60 seconds, disable AOF -> Option C

4. Quick Check:

   Fast recovery + 1 min loss = RDB every 60s [OK]

Hint: RDB snapshots match fast recovery with some data loss [OK]

Common Mistakes:

• Choosing AOF for fast recovery despite slower startup
• Enabling both causing unnecessary overhead
• Disabling persistence risking total data loss