# What's the difference between a binary search tree and a binary heap?

These two seem very similar and have almost an identical structure. What's the difference? What are the runtime complexities of each?

-
The expression "runtime complexity of [data structure]" does not make any sense. – Raphael Apr 9 '15 at 21:34

Heap just guarantees that elements on higher levels are greater (for max-heap) or smaller (for min-heap) than elements on lower levels, whereas BST guarantees order (from "left" to "right"). If you want sorted elements, go with BST.by Dante is not a geek

Heap is better at findMin/findMax (O(1)), while BST is good at all finds (O(logN)). Insert is O(logN) for both structures. If you only care about findMin/findMax (e.g. priority-related), go with heap. If you want everything sorted, go with BST.

by xysun

-
I think BST is better in findMin & findMax stackoverflow.com/a/27074221/764592 – Yeo Nov 22 '14 at 5:50
I think this is just a common misconception. A binary tree can be easily modified to find min and max as pointed by Yeo. This is actually a restriction of the heap: the only efficient find is min or max. The true advantage of the heap is O(1) average insert as I explain: stackoverflow.com/a/29548834/895245 – Ciro Santilli 巴拿馬文件 六四事件 法轮功 Jun 20 '15 at 5:01

Both binary search trees and binary heaps are both in the set of trees and are tree-based data structures.

Heaps require the nodes to have a priority over their children. In a max heap, each node's children must be less than itself. This is the opposite for a min heap:

Binary search trees (BST) follow a specific ordering (pre-order, in-order, post-order) among sibling nodes. The tree must be sorted, unlike heaps:

BST have average of $O(\log n)$ for insertion, deletion, and search.
Binary Heaps have average $O(1)$ for findMin/findMax and $O(\log n)$ for insertion and deletion.

-
Welcome to Computer Science! Note that you can use LaTeX here to typeset mathematics in a more readable way. See here for a short introduction. – FrankW Jun 20 '14 at 7:17
Insertion into binary heaps is $O(\log n)$, not $O(1)$. What is $O(1)$ is extract_min/extract_max. – FrankW Jun 20 '14 at 7:18

With data structure one has to distinguish levels of concern.

1. The abstract data structures (objects stored, their operations) in this question are different. One implements a priority queue, the other a set. A priority queue is not interested in finding an arbitrary element, only the one with largest priority.

2. The concrete implementation of the structures. Here on first sight both are (binary) trees, with different structural properties though. Both the relative ordering of the keys and the possible global structures differ. (Somewhat imprecise, in a BST keys are ordered left-to-right, in a heap they are ordered top-down.) As IPlant correctly remarks an heap should also be "complete".

3. There is a final difference in the low level implementation. A (unbalanced) binary search-tree has a standard implementation using pointers. A binary heap to the contrary has an efficient implementation using an array (precisely because of the restricted structure).

-

Advantages of binary heap over a balanced BST

Advantage of BST over binary heap

• search for arbitrary elements O(log(n)), O(n) for heap, in which the only fast search is for the largest element O(1). This is the killer feature of BSTs.

"False" advantage of heap over BST

• heap is O(1) to find max, BST O(log(n)).

This is a common misconception, because it is trivial to modify a balanced BST to keep track of the largest element, and update it whenever that element could be changed: on insertion of a larger one swap, on removal find the second largest. http://stackoverflow.com/questions/7878622/can-we-use-binary-search-tree-to-simulate-heap-operation (mentioned by Yeo).

Actually, this is a limitation of heaps: the only efficient search is that for the largest element.

Average binary heap insert is O(1)

Sources:

Intuitive argument:

• bottom tree levels have exponentially more elements than top levels, so new elements are almost certain to go at the bottom
• heap insertion starts from the bottom, BST must start from the top

In a binary heap, increasing the value at a given index is also O(1) for the same reason. But if you want to do that, it is likely that you will want to keep an extra index up-to-date on heap operations http://stackoverflow.com/questions/17009056/how-to-implement-ologn-decrease-key-operation-for-min-heap-based-priority-queu e.g. for Dijikstra. Possible at no extra time cost.

BST cannot be efficiently implemented on an array

Heap operations only need to bubble up or down a single tree branch.

Keeping a BST balanced requires tree rotations, which can change the top element for another one, and would require moving the entire array around.

Philosophy

• BSTs maintain a global property between a parent and all descendants (left smaller, right bigger).

The top node of a balanced BST is the middle element, which requires global knowledge to maintain (knowing how many smaller and larger elements are there).

This global property is more expensive to maintain (log n insert), but gives more powerful searches (log n search).

• Heaps maintain a local property between parent and direct children (parent > children).

The top note of a heap is the big element, which only requires local knowledge to maintain (knowing your parent).

A doubly linked list can be seen as subset of the heap where first item has greatest priority, so let's compare them here as well:

• insertion:
• position:
• doubly linked list: the inserted item must be either the first or last, as we only have pointers to those elements.
• binary heap: the inserted item can end up in any position. Less restrictive than heap.
• time:
• doubly linked list: O(1) worst case we have pointers to the items, and the update is really simple
• binary heap: O(1) average, thus worse. Tradeoff for having more general insertion position.
• search: O(n) for both

An use case for this is when the key of the heap is the current timestamp: in that case, new entries will always go to the beginning of the list. So we can even forget the exact timestamp altogether, and just keep the position in the list as the priority.

This can be used to implement an LRU cache. Just like for heap applications like Dijkstra, you will want to keep an additional hashmap from the key to the corresponding node of the list, to find which node to update quickly.

Similar question on SO: http://stackoverflow.com/questions/6147242/heap-vs-binary-search-tree-bst

-
Great answer. Common application of heap are median, k min, top k elements. For these most common operation remove min then insert(usually we have small heap with few pure insert operations). So seems like in practice, for these algorithms it does not outperform BST. – yura Jun 19 at 19:25

On top of the previous answers, the heap must have the heap structure property; the tree must be full, and the bottom most layer, which cannot always be full, must be filled leftmost to rightmost with no gaps.

-

A Heap a number on top MUST be bigger than it's children.

A BST the numbers to the left MUST be smaller than its parent. The numbers on the right must be bigger than its parent.

A BST is MUCH better for a search where you must find a specific number in general IMO. Since it slowly pinpoints where the number is if it exists.

A Heap on the other hand you will have to check both each side because the number/value you are looking for may exist else where. WHILE on a BST if it isn't in a particular place you know it doesn't exist in this tree.

-
What does this add to the previous answers? – dfeuer Mar 18 '15 at 1:00
Thanks for taking the time to contribute an answer but that time would have been better spent writing something that added to the existing answers, rather than duplicating them. It's also not very useful to inject opinion ("IMO") where concrete performance analysis could have been used (general find in a BST is $O(\log n)$ vs $O(n)$ in a heap) or to describe searching in a BST ($O(\log n)$) as "slow". – David Richerby Mar 18 '15 at 7:43
This was answered the day before. It's over already. – bfs Mar 18 '15 at 23:38