Why analytics drive product decisions in Firebase - Performance Analysis

Time Complexity: Why analytics drive product decisions

O(n)

Understanding Time Complexity

We want to understand how the time to gather and process analytics data changes as more users interact with a product.

How does the number of users affect the work Firebase does to collect and analyze data?

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

const analytics = getAnalytics(app);

function logUserEvent(userId, event) {
  logEvent(analytics, event, { userId: userId });
}

// Called each time a user triggers an event

This code logs an event for each user action to Firebase Analytics.

Identify Repeating Operations

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

• Primary operation: logEvent call to send user event data to Firebase Analytics.
• How many times: Once per user event triggered in the app.

How Execution Grows With Input

Each new user event causes one logEvent call, so the total work grows as more events happen.

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

Pattern observation: The number of API calls grows directly with the number of user events.

Final Time Complexity

Time Complexity: O(n)

This means the time to log analytics grows in direct proportion to the number of user events.

Common Mistake

[X] Wrong: "Logging analytics events happens all at once, so time doesn't grow with more users."

[OK] Correct: Each event triggers a separate call, so more users and events mean more calls and more time.

Interview Connect

Understanding how analytics scale helps you design systems that handle growing user activity smoothly.

Self-Check

"What if we batch multiple user events into one logEvent call? How would the time complexity change?"