Merge Sort as Divide and Conquer in DSA Java - Time & Space Complexity

Time Complexity: Merge Sort as Divide and Conquer

O(n log n)

Understanding Time Complexity

We want to understand how the time taken by merge sort changes as the list size grows.

How does splitting and merging affect the total work done?

Scenario Under Consideration

Analyze the time complexity of the following merge sort code.

public void mergeSort(int[] arr, int left, int right) {
  if (left < right) {
    int mid = (left + right) / 2;
    mergeSort(arr, left, mid);
    mergeSort(arr, mid + 1, right);
    merge(arr, left, mid, right);
  }
}
    

This code splits the array into halves, sorts each half, then merges them back.

Identify Repeating Operations

Look at the parts that repeat as the input grows.

• Primary operation: Splitting the array and merging sorted halves.
• How many times: The array is split into halves repeatedly until single elements remain, then merged back up.

How Execution Grows With Input

Each split divides the array in half, and merging takes time proportional to the size of the current part.

Input Size (n)	Approx. Operations
10	About 40 merges and splits combined
100	About 700 merges and splits combined
1000	About 10,000 merges and splits combined

Pattern observation: The work grows a bit faster than just doubling; it grows by n times log n.

Final Time Complexity

Time Complexity: O(n log n)

This means the time grows a little more than linearly, because the list is split many times and merged.

Common Mistake

[X] Wrong: "Merge sort is just like a simple loop, so it should be O(n)."

[OK] Correct: Merge sort splits the list many times and merges each part, so the total work adds up more than a single pass.

Interview Connect

Understanding merge sort's time helps you explain how divide and conquer works and why it is efficient for sorting large lists.

Self-Check

"What if we changed merge sort to split the array into three parts instead of two? How would the time complexity change?"

Practice

1. What is the main idea behind the Merge Sort algorithm in the context of divide and conquer?

easy

A. Select a pivot and partition the array around it

B. Sort the array by repeatedly swapping adjacent elements

C. Divide the array into halves, sort each half, then merge them

D. Build a heap and extract elements in sorted order

Solution

1. Step 1: Understand divide and conquer in Merge Sort

   Merge Sort splits the array into two halves recursively until single elements remain.

2. Step 2: Merge sorted halves

   It then merges these sorted halves back together to form a sorted array.

3. Final Answer:

   Divide the array into halves, sort each half, then merge them -> Option C

4. Quick Check:

   Divide and conquer = split, sort, merge [OK]

Hint: Remember: split, sort halves, then merge [OK]

Common Mistakes:

• Confusing Merge Sort with Bubble Sort
• Thinking Merge Sort uses pivot like Quick Sort
• Ignoring the merge step after dividing

2. Which of the following is the correct way to declare the merge function header in Java for merging two sorted subarrays in Merge Sort?

easy

A. int merge(int arr[], int start, int end)

B. void merge(int[] arr, int left, int mid, int right)

C. void merge(int arr[], int low, int high)

D. int merge(int[] arr, int left, int right)

Solution

1. Step 1: Identify parameters needed for merging

   The merge function needs the array and indices: left, mid, right to merge two halves.

2. Step 2: Check method signature correctness

   It returns void and takes int[] arr, int left, int mid, int right as parameters.

3. Final Answer:

   void merge(int[] arr, int left, int mid, int right) -> Option B

4. Quick Check:

   Correct merge signature = void merge(arr, left, mid, right) [OK]

Hint: Merge needs array and three indices: left, mid, right [OK]

Common Mistakes:

• Using wrong parameter names or missing mid index
• Returning int instead of void
• Confusing start/end with left/right without mid

3. What will be the output of the following Java code snippet using Merge Sort on the array [4, 1, 3, 9, 7]?

int[] arr = {4, 1, 3, 9, 7};
mergeSort(arr, 0, arr.length - 1);
System.out.println(Arrays.toString(arr));

medium

A. [1, 4, 3, 7, 9]

B. [4, 1, 3, 7, 9]

C. [9, 7, 4, 3, 1]

D. [1, 3, 4, 7, 9]

Solution

1. Step 1: Apply Merge Sort to the array

   Merge Sort divides and merges to sort: [4,1,3,9,7] -> [1,3,4,7,9]

2. Step 2: Verify final sorted array

   The sorted array is ascending: [1, 3, 4, 7, 9]

3. Final Answer:

   [1, 3, 4, 7, 9] -> Option D

4. Quick Check:

   Sorted array = ascending order [OK]

Hint: Merge Sort always outputs sorted ascending array [OK]

Common Mistakes:

• Confusing merge step output with partial arrays
• Assuming original order remains
• Mixing up ascending and descending order

4. Identify the error in this Merge Sort merge function snippet:

void merge(int[] arr, int left, int mid, int right) {
  int n1 = mid - left;
  int n2 = right - mid;
  int[] L = new int[n1];
  int[] R = new int[n2];
  for (int i = 0; i < n1; i++) L[i] = arr[left + i];
  for (int j = 0; j < n2; j++) R[j] = arr[mid + 1 + j];
  // merging logic follows...
}

medium

A. Incorrect calculation of n1 size

B. Wrong copying of elements into R array

C. Missing return statement in void method

D. Using < instead of <= in for loops

Solution

1. Step 1: Check size calculations for subarrays

   n1 should be mid - left + 1 and n2 should be right - mid to cover all elements.

2. Step 2: Identify impact of wrong sizes

   Incorrect sizes cause array index errors or missing elements during merge.

3. Final Answer:

   Incorrect calculation of n1 size -> Option A

4. Quick Check:

   Sizes must include mid element [OK]

Hint: Remember: n1 = mid-left+1, n2 = right-mid [OK]

Common Mistakes:

• Forgetting +1 in n1 size calculation
• Copying elements starting at wrong index
• Confusing loop bounds with <= instead of <

5. Given an array with many duplicate values, how should the merge step in Merge Sort be adapted to maintain stability (preserve original order of equal elements)?

hard

A. When elements are equal, copy from the left subarray first

B. When elements are equal, copy from the right subarray first

C. Skip duplicates during merge to reduce array size

D. Sort duplicates separately after merge

Solution

1. Step 1: Understand stability in sorting

   Stable sort keeps equal elements in original order.

2. Step 2: Apply stability rule in merge step

   When equal, copy element from left subarray first to preserve order.

3. Final Answer:

   When elements are equal, copy from the left subarray first -> Option A

4. Quick Check:

   Left first on equals = stable merge [OK]

Hint: Copy left element first on equal values to keep stability [OK]

Common Mistakes:

• Copying right element first breaks stability
• Removing duplicates during merge
• Sorting duplicates separately after merge