Why Intervals Are a Common Problem Pattern in DSA Javascript - Performance Analysis

Time Complexity: Why Intervals Are a Common Problem Pattern

O(n log n)

Understanding Time Complexity

Intervals problems often involve checking or merging ranges, which requires careful analysis of how many times we process each interval.

We want to understand how the number of intervals affects the work done by the algorithm.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

function mergeIntervals(intervals) {
  intervals.sort((a, b) => a[0] - b[0]);
  const merged = [];
  for (const interval of intervals) {
    if (!merged.length || merged[merged.length - 1][1] < interval[0]) {
      merged.push(interval);
    } else {
      merged[merged.length - 1][1] = Math.max(merged[merged.length - 1][1], interval[1]);
    }
  }
  return merged;
}
    

This code merges overlapping intervals by first sorting them and then combining where needed.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Sorting the intervals and then looping through each interval once.
• How many times: Sorting takes multiple comparisons (depends on n log n), then the loop runs once for each interval (n times).

How Execution Grows With Input

As the number of intervals increases, sorting takes more time, and the merging loop grows linearly.

Input Size (n)	Approx. Operations
10	About 10 * log 10 + 10 ≈ 43 operations
100	About 100 * log 100 + 100 ≈ 700 operations
1000	About 1000 * log 1000 + 1000 ≈ 10,000 operations

Pattern observation: The sorting dominates and grows faster than the simple loop, roughly n log n growth.

Final Time Complexity

Time Complexity: O(n log n)

This means the time needed grows a bit faster than the number of intervals because of sorting, but the merging step is just a simple pass.

Common Mistake

[X] Wrong: "Merging intervals is always O(n) because we just loop once."

[OK] Correct: Sorting the intervals first takes more time, so the total work is more than just one loop.

Interview Connect

Understanding how sorting and looping combine helps you explain your approach clearly and shows you know what makes interval problems tricky.

Self-Check

"What if the intervals were already sorted? How would the time complexity change?"

Practice

1. Why are interval problems common in algorithms and data structures?

easy

A. Because intervals never overlap in any problem

B. Because intervals are always sorted by default

C. Because intervals only deal with single numbers

D. Because many real-world problems involve ranges or periods of time

Solution

1. Step 1: Understand what intervals represent

   Intervals represent ranges, such as time periods or numeric ranges, which are common in real-world scenarios.

2. Step 2: Connect intervals to problem patterns

   Many problems require managing overlapping or merging these ranges, making intervals a common pattern.

3. Final Answer:

   Because many real-world problems involve ranges or periods of time -> Option D

4. Quick Check:

   Intervals = ranges in real life [OK]

Hint: Think about real-life ranges like meetings or bookings [OK]

Common Mistakes:

• Assuming intervals are always sorted
• Thinking intervals never overlap
• Believing intervals are single points

2. Which of the following is the correct syntax to represent an interval in JavaScript as an object with start and end properties?

easy

A. const interval = (1, 5);

B. const interval = [start: 1, end: 5];

C. const interval = {start: 1, end: 5};

D. const interval = {1, 5};

Solution

1. Step 1: Recall JavaScript object syntax

   Objects use curly braces with key-value pairs like {key: value}.

2. Step 2: Match the correct interval representation

   The interval with start and end keys is correctly written as {start: 1, end: 5}.

3. Final Answer:

   const interval = {start: 1, end: 5}; -> Option C

4. Quick Check:

   Object syntax = {key: value} [OK]

Hint: Use curly braces and key-value pairs for objects [OK]

Common Mistakes:

• Using square brackets for objects
• Using parentheses for objects
• Missing keys in object syntax

3. What will be the output of the following JavaScript code?

const intervals = [
  {start: 1, end: 3},
  {start: 2, end: 6},
  {start: 8, end: 10}
];

const merged = [];
intervals.sort((a, b) => a.start - b.start);

for (const interval of intervals) {
  if (!merged.length || merged[merged.length - 1].end < interval.start) {
    merged.push(interval);
  } else {
    merged[merged.length - 1].end = Math.max(merged[merged.length - 1].end, interval.end);
  }
}

console.log(merged);

medium

A. [{start: 1, end: 6}, {start: 8, end: 10}]

B. [{start: 1, end: 3}, {start: 2, end: 6}, {start: 8, end: 10}]

C. [{start: 1, end: 10}]

D. [{start: 2, end: 6}, {start: 8, end: 10}]

Solution

1. Step 1: Sort intervals by start

   Intervals are sorted as [{1,3}, {2,6}, {8,10}].

2. Step 2: Merge overlapping intervals

   First interval added. Second overlaps with first, so merge to {1,6}. Third does not overlap, so added as is.

3. Final Answer:

   [{start: 1, end: 6}, {start: 8, end: 10}] -> Option A

4. Quick Check:

   Merged intervals = [{1,6}, {8,10}] [OK]

Hint: Sort by start, then merge overlapping intervals [OK]

Common Mistakes:

• Not sorting intervals before merging
• Overwriting intervals incorrectly
• Missing to merge overlapping intervals

4. The following code is intended to merge overlapping intervals but has a bug. What is the bug?

const intervals = [
  {start: 1, end: 4},
  {start: 3, end: 5}
];

const merged = [];
for (const interval of intervals) {
  if (!merged.length || merged[merged.length - 1].end < interval.start) {
    merged.push(interval);
  } else {
    merged[merged.length - 1].end = Math.max(merged[merged.length - 1].end, interval.end);
  }
}

console.log(merged);

medium

A. Using Math.min instead of Math.max in merging

B. Intervals are not sorted before merging

C. Pushing intervals without checking overlap

D. Not initializing merged as an array

Solution

1. Step 1: Check if intervals are sorted

   The code does not sort intervals before merging, which can cause incorrect merges.

2. Step 2: Understand impact of missing sort

   Without sorting, overlapping intervals may not be adjacent, so merging logic fails.

3. Final Answer:

   Intervals are not sorted before merging -> Option B

4. Quick Check:

   Sort intervals first [OK]

Hint: Always sort intervals by start before merging [OK]

Common Mistakes:

• Forgetting to sort intervals
• Using wrong Math function
• Ignoring overlap checks

5. Given a list of intervals representing booked meeting times, how would you find the minimum number of meeting rooms required to hold all meetings without overlap?

hard

A. Sort intervals by start time, use a min-heap to track end times, count max rooms needed

B. Sort intervals by end time, merge all intervals, count merged intervals

C. Count intervals with the same start time only

D. Use a stack to push all intervals and pop when overlap occurs

Solution

1. Step 1: Sort intervals by start time

   Sorting helps process meetings in chronological order.

2. Step 2: Use a min-heap to track earliest ending meeting

   Min-heap stores end times; if a meeting starts after earliest end, reuse room; else add room.

3. Step 3: Count maximum rooms used simultaneously

   The heap size at any time shows rooms needed; max size is minimum rooms required.

4. Final Answer:

   Sort intervals by start time, use a min-heap to track end times, count max rooms needed -> Option A

5. Quick Check:

   Min rooms = max overlapping intervals [OK]

Hint: Track earliest end times with min-heap to count rooms [OK]

Common Mistakes:

• Merging intervals instead of counting overlaps
• Ignoring meeting end times
• Using stack instead of min-heap