6.4. The Binary Search¶

It is possible to take greater advantage of the ordered vector if we are clever with our comparisons. In the sequential search, when we compare against the first item, there are at most \(n-1\) more items to look through if the first item is not what we are looking for. Instead of searching the vector in sequence, a binary search will start by examining the middle item. If that item is the one we are searching for, we are done. If it is not the correct item, we can use the ordered nature of the vector to eliminate half of the remaining items. If the item we are searching for is greater than the middle item, we know that the entire lower half of the vector as well as the middle item can be eliminated from further consideration. The item, if it is in the vector, must be in the upper half.

We can then repeat the process with the upper half. Start at the middle item and compare it against what we are looking for. Again, we either find it or split the vector in half, therefore eliminating another large part of our possible search space. Figure 3 shows how this algorithm can quickly find the value 54. The complete function is shown in CodeLens 3.

Figure 3: Binary Search of an Ordered vector of Integers

Binary Search of an Ordered List (search3)

A similar implementation can be carried out using vectors in C++.

Before we move on to the analysis, we should note that this algorithm is a great example of a divide and conquer strategy. Divide and conquer means that we divide the problem into smaller pieces, solve the smaller pieces in some way, and then reassemble the whole problem to get the result. When we perform a binary search of a list, we first check the middle item. If the item we are searching for is less than the middle item, we can simply perform a binary search of the left half of the original list. Likewise, if the item is greater, we can perform a binary search of the right half. Either way, this is a recursive call to the binary search function passing a smaller list. CodeLens 4 shows this recursive version.

A Binary Search--Recursive Version (search4)

There is a vector initializer within C++ that can be used much like python slices, however this can only be used when new vectors are created.

#include <iostream>
#include <vector>
using namespace std;

bool binarySearch(vector<int> alist, int item) {
      if (alist.size() == 0) {
              return false;
      } else {
              int midpoint = alist.size() / 2;
              if (alist[midpoint] == item) {
                      return true;
              } else {
                      if (item < alist[midpoint]) {
                              vector<int> lefthalf(alist.begin(), alist.begin() + midpoint);
                              return binarySearch(lefthalf, item);
                      } else {
                              vector<int> righthalf(
                                      alist.begin() + midpoint + 1, alist.end());
                              return binarySearch(righthalf, item);
                      }
              }
      }
}

int main() {
      // Using static array to initialize a vector
      static const int arr[] = {0, 1, 2, 8, 13, 17, 19, 32, 42};
      vector<int> alist(arr, arr + sizeof(arr) / sizeof(arr[0]));

cout << binarySearch(alist, 3) << endl;
      cout << binarySearch(alist, 13) << endl;

return 0;
}

6.4.1. Analysis of Binary Search¶

To analyze the binary search algorithm, we need to recall that each comparison eliminates about half of the remaining items from consideration. What is the maximum number of comparisons this algorithm will require to check the entire list? If we start with n items, about \(\frac{n}{2}\) items will be left after the first comparison. After the second comparison, there will be about \(\frac{n}{4}\). Then \(\frac{n}{8}\), \(\frac{n}{16}\), and so on. How many times can we split the list? Table 3 helps us to see the answer.

**Table 3: Tabular Analysis for a Binary Search**¶
Comparisons	Approximate Number of Items Left
1	\(\frac {n}{2}\)
2	\(\frac {n}{4}\)
3	\(\frac {n}{8}\)
…
i	\(\frac {n}{2^i}\)

When we split the list enough times, we end up with a list that has just one item. Either that is the item we are looking for or it is not. Either way, we are done. The number of comparisons necessary to get to this point is i where \(\frac {n}{2^i} =1\). Solving for i gives us \(i=\log n\). The maximum number of comparisons is logarithmic with respect to the number of items in the list. Therefore, the binary search is \(O(\log n)\).

One additional analysis issue needs to be addressed. In the recursive solution shown above, the recursive call,

binarySearch(alist[:midpoint],item)

uses the slice operator to create the left half of the list that is then passed to the next invocation (similarly for the right half as well). The analysis that we did above assumed that the slice operator takes constant time. However, we know that the slice operator in Python is actually O(k). This means that the binary search using slice will not perform in strict logarithmic time. Luckily this can be remedied by passing the list along with the starting and ending indices. The indices can be calculated as we did in Listing 3. This is especially relevant in C++, where we are initializing a new vector for each split of our list. To truly optimize this algorithm, we could use an array and manually keep track of start and end indices of our array. Below is an example of such an implementation.

Even though a binary search is generally better than a sequential search, it is important to note that for small values of n, the additional cost of sorting is probably not worth it. In fact, we should always consider whether it is cost effective to take on the extra work of sorting to gain searching benefits. If we can sort once and then search many times, the cost of the sort is not so significant. However, for large lists, sorting even once can be so expensive that simply performing a sequential search from the start may be the best choice.

Self Check

11, 5, 6, 8
Looks like you might be guilty of an off-by-one error. Remember the first position is index 0.
12, 6, 11, 8
Binary search starts at the midpoint and halves the list each time.
3, 5, 6, 8
Binary search does not start at the beginning and search sequentially, its starts in the middle and halves the list after each compare.
18, 12, 6, 8
It appears that you are starting from the end and halving the list each time.

11, 14, 17
Looks like you might be guilty of an off-by-one error. Remember the first position is index 0.
18, 17, 15
Remember binary search starts in the middle and halves the list.
14, 17, 15
Looks like you might be off by one, be careful that you are calculating the midpont using integer arithmetic.
12, 17, 15
Binary search starts at the midpoint and halves the list each time. It is done when the list is empty.

Next Section - 6.5. Hashing