EXPIRE and TTL for time-to-live in Redis - Time & Space Complexity

Time Complexity: EXPIRE and TTL for time-to-live

O(1)

Understanding Time Complexity

When using Redis commands like EXPIRE and TTL, it's important to know how their speed changes as your data grows.

We want to understand how long these commands take when you have many keys or set many expirations.

Scenario Under Consideration

Analyze the time complexity of the following Redis commands.

SET session:user123 "data"
EXPIRE session:user123 3600
TTL session:user123
    

This code sets a key, assigns it a time-to-live of one hour, and then checks how much time is left before it expires.

Identify Repeating Operations

Look for any repeated steps or loops inside these commands.

• Primary operation: Checking or setting expiration on a single key.
• How many times: Each command works on one key at a time, no loops over multiple keys.

How Execution Grows With Input

These commands handle one key at a time, so their work does not increase with the total number of keys.

Input Size (n)	Approx. Operations
10 keys	Same small number of steps per command
100 keys	Still same small number of steps per command
1000 keys	No increase in steps per command

Pattern observation: The time to run EXPIRE or TTL stays about the same no matter how many keys exist.

Final Time Complexity

Time Complexity: O(1)

This means setting or checking expiration takes the same short time regardless of how many keys you have.

Common Mistake

[X] Wrong: "Checking TTL gets slower as I add more keys because Redis must look through all keys."

[OK] Correct: Redis stores expiration info efficiently, so TTL only checks one key directly without scanning others.

Interview Connect

Knowing that EXPIRE and TTL run in constant time helps you explain how Redis handles time-based data efficiently, a useful skill in many real projects.

Self-Check

"What if we wanted to set expiration on many keys at once? How would that affect the time complexity?"

Practice

1. What does the Redis command EXPIRE key 60 do?

easy

A. Returns the remaining time to live for the key.

B. Immediately deletes the key named 'key'.

C. Sets the key to expire and be deleted after 60 seconds.

D. Renames the key to '60'.

Solution

1. Step 1: Understand the EXPIRE command

   The EXPIRE command sets a countdown timer on a key in seconds.

2. Step 2: Apply the command to the example

   Here, EXPIRE key 60 sets the key to expire after 60 seconds.

3. Final Answer:

   Sets the key to expire and be deleted after 60 seconds. -> Option C

4. Quick Check:

   EXPIRE sets countdown = A [OK]

Hint: EXPIRE sets time in seconds before deletion [OK]

Common Mistakes:

• Thinking EXPIRE deletes immediately
• Confusing EXPIRE with TTL command
• Assuming EXPIRE renames keys

2. Which of the following is the correct syntax to check the remaining time to live of a key named session in Redis?

easy

A. TTL session

B. EXPIRE session

C. GETTTL session

D. TIMELEFT session

Solution

1. Step 1: Identify the command to check TTL

   The Redis command to check remaining time is TTL key.

2. Step 2: Match the syntax with the key name

   For key session, the correct command is TTL session.

3. Final Answer:

   TTL session -> Option A

4. Quick Check:

   TTL command syntax = D [OK]

Hint: TTL shows remaining seconds before expiry [OK]

Common Mistakes:

• Using EXPIRE to check TTL
• Assuming GETTTL is a Redis command
• Using TIMELEFT which does not exist

3. Consider the following Redis commands executed in order:

SET temp "data"
EXPIRE temp 10
TTL temp

What will the TTL temp command return immediately after setting the expire?

medium

A. Error

B. -1

C. 0

D. 10

Solution

1. Step 1: Set key and expire time

   The key temp is set with value "data" and an expire time of 10 seconds.

2. Step 2: Check TTL immediately after EXPIRE

   Immediately after setting expire, TTL returns the remaining seconds, which is 10.

3. Final Answer:

   10 -> Option D

4. Quick Check:

   TTL after EXPIRE = 10 [OK]

Hint: TTL returns seconds left right after EXPIRE [OK]

Common Mistakes:

• Expecting TTL to return -1 (no expire)
• Thinking TTL returns 0 immediately
• Assuming TTL causes an error if key exists

4. You run the following commands:

SET user "Alice"
EXPIRE user -5
TTL user

What is the result of TTL user and why?

medium

A. -2 because key is deleted immediately

B. Error due to invalid expire time

C. -1 because negative expire removes expiration

D. 5 because negative is treated as positive

Solution

1. Step 1: Understand EXPIRE with negative time

   Setting EXPIRE with a negative value deletes the key immediately.

2. Step 2: Check TTL after immediate deletion

   TTL returns -2 when the key does not exist.

3. Final Answer:

   -2 because key is deleted immediately -> Option A

4. Quick Check:

   Negative EXPIRE deletes key, TTL = -2 [OK]

Hint: Negative EXPIRE deletes key, TTL returns -2 [OK]

Common Mistakes:

• Thinking negative expire removes expiration but keeps key
• Expecting TTL to return -1 for no expire
• Assuming negative expire causes error

5. You want to set a key cache with a value and ensure it expires in 30 seconds only if it does not already have an expiration. Which Redis command sequence achieves this safely?

hard

A. SET cache "value" NX EX 30

B. SET cache "value"
TTL cache
EXPIRE cache 30 if TTL is -1

C. SET cache "value" EX 30
EXPIRE cache 30

D. SET cache "value"
EXPIRE cache 30

Solution

1. Step 1: Understand the requirement

   We want to set the key and only add expiration if none exists (TTL = -1).

2. Step 2: Analyze options

   SET cache "value" TTL cache EXPIRE cache 30 if TTL is -1 checks TTL first, then sets EXPIRE only if TTL is -1, ensuring no overwrite of existing expiration.

3. Final Answer:

   SET cache "value" TTL cache EXPIRE cache 30 if TTL is -1 -> Option B

4. Quick Check:

   Check TTL before EXPIRE to avoid overwriting [OK]

Hint: Check TTL before EXPIRE to avoid overwriting [OK]

Common Mistakes:

• Using NX option which only affects key existence
• Setting EXPIRE twice unnecessarily
• Not checking TTL before setting EXPIRE