User properties in Firebase - Time & Space Complexity

Time Complexity: User properties

O(n)

Understanding Time Complexity

When working with user properties in Firebase, it's important to know how the time to set or update these properties changes as you add more users.

We want to understand how the number of users affects the time it takes to update their properties.

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

const users = [user1, user2, user3, /* ... */];

users.forEach(user => {
  firebase.analytics().setUserProperties({
    favorite_color: user.favorite_color
  });
});
    

This code sets a user property called "favorite_color" for each user in a list.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: Calling setUserProperties for each user.
• How many times: Once per user in the list.

How Execution Grows With Input

Each user requires one call to update their properties, so the total calls grow directly with the number of users.

Input Size (n)	Approx. Api Calls/Operations
10	10 calls
100	100 calls
1000	1000 calls

Pattern observation: The number of operations increases in a straight line as the number of users increases.

Final Time Complexity

Time Complexity: O(n)

This means the time to update user properties grows directly with the number of users.

Common Mistake

[X] Wrong: "Updating user properties happens all at once, so time stays the same no matter how many users there are."

[OK] Correct: Each user property update is a separate call, so more users mean more calls and more time.

Interview Connect

Understanding how operations scale with input size shows you can think about efficiency and resource use, a key skill in cloud work.

Self-Check

"What if we batch user property updates instead of calling setUserProperties for each user? How would the time complexity change?"