Unique visitor tracking with sets in Redis - Time & Space Complexity

Time Complexity: Unique visitor tracking with sets

O(n)

Understanding Time Complexity

When tracking unique visitors, we want to know how the work grows as more visitors come in.

We ask: How much time does it take to add and count unique visitors as the list grows?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

SADD unique_visitors user1
SADD unique_visitors user2
SADD unique_visitors user3

SCARD unique_visitors
    

This code adds visitors to a set and then counts how many unique visitors there are.

Identify Repeating Operations

• Primary operation: Adding a visitor to the set with SADD.
• How many times: Once per visitor added.
• Counting operation: SCARD counts unique visitors once.

How Execution Grows With Input

Each new visitor is checked and added if unique. Counting is quick regardless of size.

Input Size (n)	Approx. Operations
10	10 adds + 1 count
100	100 adds + 1 count
1000	1000 adds + 1 count

Pattern observation: Adding visitors grows linearly; counting stays constant time.

Final Time Complexity

Time Complexity: O(n)

This means the time to add visitors grows directly with the number of visitors.

Common Mistake

[X] Wrong: "The total time to track n unique visitors is O(1)."

[OK] Correct: Although each SADD is O(1), performing n additions requires O(n) time total.

Interview Connect

Understanding how adding unique items scales helps you explain data handling in real apps clearly and confidently.

Self-Check

"What if we used a list instead of a set to track visitors? How would the time complexity change?"

Practice

1. What is the main advantage of using Redis sets for unique visitor tracking?

easy

A. They automatically prevent duplicate visitor IDs.

B. They store visitor data in sorted order.

C. They allow storing large text data efficiently.

D. They provide built-in encryption for visitor IDs.

Solution

1. Step 1: Understand Redis sets behavior

   Redis sets store unique elements only, so duplicates are not saved.

2. Step 2: Relate to visitor tracking

   This means each visitor ID is stored once, ensuring uniqueness automatically.

3. Final Answer:

   They automatically prevent duplicate visitor IDs. -> Option A

4. Quick Check:

   Redis sets = unique elements [OK]

Hint: Remember: sets never store duplicates [OK]

Common Mistakes:

• Thinking sets store elements in order
• Confusing sets with lists or hashes
• Assuming sets encrypt data automatically

2. Which Redis command correctly adds a visitor ID 'user123' to a set named 'visitors'?

easy

A. SET visitors user123

B. ADD visitors user123

C. SADD visitors user123

D. APPEND visitors user123

Solution

1. Step 1: Identify the correct command to add to a set

   The Redis command to add members to a set is SADD.

2. Step 2: Check syntax correctness

   SADD visitors user123 adds 'user123' to the 'visitors' set correctly.

3. Final Answer:

   SADD visitors user123 -> Option C

4. Quick Check:

   SADD adds members to sets [OK]

Hint: Use SADD to add members to sets [OK]

Common Mistakes:

• Using SET which is for strings, not sets
• Using ADD which is invalid in Redis
• Using APPEND which is for strings

3. Given the following Redis commands executed in order:

SADD visitors user1
SADD visitors user2
SADD visitors user1
SCARD visitors

What will be the output of SCARD visitors?

medium

A. 2

B. 0

C. 1

D. 3

Solution

1. Step 1: Analyze SADD commands

   First adds 'user1', second adds 'user2', third tries to add 'user1' again (ignored as duplicate).

2. Step 2: Understand SCARD output

   SCARD returns the count of unique members in the set, which are 'user1' and 'user2'.

3. Final Answer:

   2 -> Option A

4. Quick Check:

   Unique visitors count = 2 [OK]

Hint: SCARD counts unique set members [OK]

Common Mistakes:

• Counting duplicates as separate members
• Confusing SCARD with SMEMBERS output
• Assuming SCARD returns all added commands count

4. You run the command SADD visitors without specifying any visitor ID. What will happen?

medium

A. A new empty set is created.

B. An error occurs due to missing member argument.

C. The command adds a null member to the set.

D. The command is ignored silently.

Solution

1. Step 1: Check SADD command requirements

   SADD requires at least one member argument to add to the set.

2. Step 2: Result of missing member argument

   Running SADD without members causes a syntax error in Redis.

3. Final Answer:

   An error occurs due to missing member argument. -> Option B

4. Quick Check:

   SADD needs members, else error [OK]

Hint: SADD must have at least one member argument [OK]

Common Mistakes:

• Assuming empty sets can be created with SADD alone
• Thinking null or empty string is added automatically
• Expecting silent failure without error

5. You want to track unique visitors for multiple days using Redis sets. Which approach correctly counts total unique visitors across days stored as sets 'day1', 'day2', and 'day3'?

hard

A. Use DEL day1 day2 day3 then SCARD total.

B. Use SINTERSTORE total day1 day2 day3 then SCARD total.

C. Use SMEMBERS day1 then count manually.

D. Use SUNIONSTORE total day1 day2 day3 then SCARD total.

Solution

1. Step 1: Understand set operations for unique visitors

   To combine unique visitors from multiple sets, use SUNIONSTORE to create a union set.

2. Step 2: Count unique visitors in combined set

   After union, SCARD on the combined set gives total unique visitors across days.

3. Final Answer:

   Use SUNIONSTORE total day1 day2 day3 then SCARD total. -> Option D

4. Quick Check:

   Union sets + SCARD = total unique visitors [OK]

Hint: Use SUNIONSTORE to combine sets before counting [OK]

Common Mistakes:

• Using SINTERSTORE which finds common visitors only
• Counting members manually instead of using SCARD
• Deleting sets before counting unique visitors