Time Complexity: Session storage pattern
O(1)
0
0
Session storage pattern in Redis - Time & Space Complexity
Understanding Time Complexity
When storing user sessions in Redis, it is important to understand how the time to save or retrieve a session changes as the number of sessions grows.
We want to know how the cost of session operations grows with more users.
Scenario Under Consideration
Analyze the time complexity of the following Redis commands used for session storage.
# Store session data as a hash
HSET session:1234 user_id 42 last_active 1680000000
# Retrieve session data
HGETALL session:1234
# Delete session when user logs out
DEL session:1234
# Set expiration for session
EXPIRE session:1234 3600
This code stores, retrieves, deletes, and expires a user session using Redis hashes and keys.
Identify Repeating Operations
Look at the main operations that happen repeatedly when managing sessions.
- Primary operation: Accessing a Redis hash for a single session key.
- How many times: Once per session operation (store, retrieve, delete).
How Execution Grows With Input
Each session operation works on one key and its hash fields, so the time depends mostly on the size of that session's data, not the total number of sessions.
| Input Size (n) | Approx. Operations |
|---|---|
| 10 sessions | About the same time per session operation |
| 100 sessions | Still about the same time per session operation |
| 1000 sessions | Still about the same time per session operation |
Pattern observation: Time per session operation stays roughly constant no matter how many sessions exist.
Final Time Complexity
Time Complexity: O(1)
This means each session operation takes about the same time regardless of how many sessions are stored.
Common Mistake
[X] Wrong: "As the number of sessions grows, retrieving one session will take longer because Redis has to look through all sessions."
[OK] Correct: Redis uses keys to directly access each session, so it does not scan all sessions. Access time stays constant.
Interview Connect
Understanding how Redis handles session storage efficiently shows you know how to design fast, scalable systems that keep user data ready without delay.
Self-Check
"What if we stored all sessions inside one big Redis hash instead of separate keys? How would the time complexity change?"