Executive summary: every year when teaching data structures I always forget how to analyze the cost of building a binary heap, which amounts to summing the heights of all the nodes in a full binary tree. So I’m writing down the (lovely) proof here in the hopes that I will remember it next time.
Suppose you have a full binary tree and you do an operation on every node, where the cost of the operation is proportional to the height of that node. That is, the cost for each of the leaves is , for each of the nodes in the next level up the cost is , and so on. We can visualize the scenario like this:
As a function of the total number of nodes , how expensive is this? We can see that is an upper bound, since there are nodes and the height of each node is at most . But it seems like it might actually be faster than this in reality, since, intuitively, most of the nodes have a height which is much smaller than .
(One specific motivation for this scenario is that we can build a binary heap from an arbitrary set of data by looping over the nodes from the bottom up and calling
reheapDown on each; in the worst case
reheapDown takes time proportional to the height of the node, as in this scenario. But it doesn’t matter if you don’t know about binary heaps.)
Let’s take the same tree and put a dollar at every node, for a total of :
Now imagine sliding all the money as far up and to the right as it will go. That is, we take each dollar, and keep moving it up as long as it is a left child. As soon as we reach a node which is a right child we stop. The tree ends up looking like this:
Now take each pile of money and move it up one step to its parent, except the money at the root of the tree, which you can put in your pocket.
And voilà! We now have exactly enough money at each node to pay for the cost of the operations, and we even have a bit left over (which we can use to buy coffee). But we started with and only shuffled money around; this shows that the total cost is actually .
Exercise for the reader: what does this have to do with the number of bit flips needed to count from to with a binary counter?
Funny and elegant solution. I remembered the result from university, but now I can eaily remember even the “proof”.
Pingback: Resumen de lecturas compartidas durante noviembre de 2017 | Vestigium