Divide and Conquer Strategy and Recurrence Relations in DSA Javascript - Time & Space Complexity

Time Complexity: Divide and Conquer Strategy and Recurrence Relations

O(n log n)

Understanding Time Complexity

Divide and conquer breaks a problem into smaller parts, solves each part, then combines results.

We want to know how the total work grows as the problem size grows.

Scenario Under Consideration

Analyze the time complexity of this recursive divide and conquer code.

function divideAndConquer(arr) {
  if (arr.length <= 1) return arr;
  const mid = Math.floor(arr.length / 2);
  const left = divideAndConquer(arr.slice(0, mid));
  const right = divideAndConquer(arr.slice(mid));
  return merge(left, right);
}

function merge(left, right) {
  // Merges two sorted arrays into one sorted array
  let result = [];
  let i = 0, j = 0;
  while (i < left.length && j < right.length) {
    if (left[i] < right[j]) {
      result.push(left[i++]);
    } else {
      result.push(right[j++]);
    }
  }
  return result.concat(left.slice(i)).concat(right.slice(j));
}
    

This code splits an array into halves, sorts each half recursively, then merges them.

Identify Repeating Operations

Look at the recursive calls and merging steps.

• Primary operation: Splitting array and merging sorted halves.
• How many times: The array is split into halves repeatedly until size 1, then merged back.

How Execution Grows With Input

Each split halves the problem, but merging takes time proportional to the current size.

Input Size (n)	Approx. Operations
10	About 10 * log2(10) ≈ 33 merges
100	About 100 * log2(100) ≈ 664 merges
1000	About 1000 * log2(1000) ≈ 9966 merges

Pattern observation: Operations grow a bit faster than linear, roughly linear times log of input size.

Final Time Complexity

Time Complexity: O(n log n)

This means the work grows a little more than linearly as input size grows, due to repeated splitting and merging.

Common Mistake

[X] Wrong: "Because the array is split in half each time, the time is just O(log n)."

[OK] Correct: Splitting reduces problem size, but merging takes linear time each level, so total work is more than just log n.

Interview Connect

Understanding divide and conquer and its time helps you explain many algorithms clearly and confidently.

Self-Check

"What if the merge step took constant time instead of linear? How would the time complexity change?"

Practice

1. What is the main idea behind the Divide and Conquer strategy in algorithms?

easy

A. Solve the problem by trying all possible solutions one by one

B. Use a single loop to iterate through all elements

C. Break the problem into smaller subproblems, solve them independently, then combine results

D. Store all intermediate results to avoid repeated calculations

Solution

1. Step 1: Understand the divide and conquer approach

   It splits a big problem into smaller parts that are easier to solve.

2. Step 2: Combine the solutions of smaller parts

   After solving subproblems, their results are merged to get the final answer.

3. Final Answer:

   Break the problem into smaller subproblems, solve them independently, then combine results -> Option C

4. Quick Check:

   Divide and conquer = split, solve, combine [OK]

Hint: Divide and conquer means split, solve, then merge results [OK]

Common Mistakes:

• Confusing divide and conquer with brute force
• Thinking it uses only one loop
• Mixing it with dynamic programming

2. Which of the following is the correct syntax for the recurrence relation of Merge Sort?

easy

A. T(n) = 3T(n/3) + O(log n)

B. T(n) = 2T(n/2) + O(n)

C. T(n) = T(n/2) + O(n^2)

D. T(n) = T(n-1) + O(1)

Solution

1. Step 1: Recall Merge Sort recurrence

   Merge Sort splits array into two halves, sorts each half, then merges in O(n).

2. Step 2: Write recurrence form

   It calls itself twice on half size (2T(n/2)) plus linear merge time O(n).

3. Final Answer:

   T(n) = 2T(n/2) + O(n) -> Option B

4. Quick Check:

   Merge Sort recurrence = 2T(n/2) + n [OK]

Hint: Merge Sort splits in two, merges in linear time [OK]

Common Mistakes:

• Using T(n-1) instead of T(n/2)
• Adding O(n^2) instead of O(n)
• Confusing with Quick Sort recurrence

3. What is the output of the following JavaScript function that uses divide and conquer?

function sumArray(arr) {
  if (arr.length === 1) return arr[0];
  const mid = Math.floor(arr.length / 2);
  return sumArray(arr.slice(0, mid)) + sumArray(arr.slice(mid));
}
console.log(sumArray([2, 4, 6, 8]));

medium

A. 20

B. 24

C. 10

D. Error

Solution

1. Step 1: Understand the function behavior

   The function splits the array into halves recursively and sums elements.

2. Step 2: Trace the calls for [2,4,6,8]

   Split into [2,4] and [6,8], sumArray([2,4]) = 6, sumArray([6,8]) = 14, total 20.

3. Final Answer:

   20 -> Option A

4. Quick Check:

   Sum of 2+4+6+8 = 20 [OK]

Hint: Divide array, sum halves, add results [OK]

Common Mistakes:

• Confusing slice indices causing wrong sums
• Assuming function returns array instead of sum
• Forgetting base case for single element

4. Identify the error in this divide and conquer function to find the maximum element:

function findMax(arr) {
  if (arr.length === 1) return arr[0];
  const mid = Math.floor(arr.length / 2);
  const leftMax = findMax(arr.slice(0, mid));
  const rightMax = findMax(arr.slice(mid));
  return leftMax > rightMax ? leftMax : rightMax;
}
console.log(findMax([]));

medium

A. Fails on empty array input causing infinite recursion

B. Incorrect comparison operator used

C. No error, works correctly

D. Slices do not split array properly

Solution

1. Step 1: Check base case for empty array

   The function does not handle empty array input, so arr.length === 0 is not checked.

2. Step 2: Understand recursion on empty array

   Calling findMax([]) leads to infinite recursion because base case is only for length 1.

3. Final Answer:

   Fails on empty array input causing infinite recursion -> Option A

4. Quick Check:

   Empty input needs base case to avoid infinite calls [OK]

Hint: Always check for empty input base case [OK]

Common Mistakes:

• Ignoring empty array edge case
• Assuming slice always returns non-empty array
• Thinking comparison operator is wrong

5. Given the recurrence relation T(n) = 3T(n/3) + n, what is the time complexity using the Master Theorem?

hard

A. O(log n)

B. O(n^2)

C. O(n)

D. O(n log n)

Solution

1. Step 1: Identify parameters for Master Theorem

   Here, a=3, b=3, f(n)=n. Calculate log_b(a) = log_3(3) = 1.

2. Step 2: Compare f(n) with n^log_b(a)

   f(n) = n and n^log_b(a) = n^1 = n, so f(n) = Theta(n^log_b(a)).

3. Step 3: Apply Master Theorem case 2

   When f(n) = Theta(n^log_b(a)), T(n) = Theta(n log n).

4. Final Answer:

   O(n log n) -> Option D

5. Quick Check:

   Master Theorem case 2 = n log n [OK]

Hint: Compare f(n) to n^log_b(a) for Master Theorem [OK]

Common Mistakes:

• Confusing log base or parameters a and b
• Choosing wrong Master Theorem case
• Ignoring the extra n term in recurrence