# Van Emde Boas tree

A **van Emde Boas tree** (Dutch pronunciation: [vɑn 'ɛmdə 'boːɑs]), also known as a **vEB tree** or **van Emde Boas priority queue**, is a tree data structure which implements an associative array with *m*-bit integer keys. It performs all operations in *O*(log *m*) time, or equivalently in *O*(log log *M*) time, where *M* = 2^{m} is the maximum number of elements that can be stored in the tree. The *M* is not to be confused with the actual number of elements stored in the tree, by which the performance of other tree data-structures is often measured. The vEB tree has good space efficiency when it contains many elements, as discussed below. It was invented by a team led by Dutch computer scientist Peter van Emde Boas in 1975.[1]

van Emde Boas tree | |
---|---|

Type | Non-binary tree |

Invented | 1975 |

Invented by | Peter van Emde Boas |

Asymptotic complexity in big O notation | |

Space | O(M) |

Search | O(log log M) |

Insert | O(log log M) |

Delete | O(log log M) |

## Supported operations

A vEB supports the operations of an *ordered associative array*, which includes the usual associative array operations along with two more *order* operations, *FindNext* and *FindPrevious*:[2]

*Insert*: insert a key/value pair with an*m*-bit key*Delete*: remove the key/value pair with a given key*Lookup*: find the value associated with a given key*FindNext*: find the key/value pair with the smallest key which is greater than a given*k**FindPrevious*: find the key/value pair with the largest key which is smaller than a given*k*

A vEB tree also supports the operations *Minimum* and *Maximum*, which return the minimum and maximum element stored in the tree respectively.[3] These both run in *O*(1) time, since the minimum and maximum element are stored as attributes in each tree.

## How it works

For the sake of simplicity, let log_{2} *m* = *k* for some integer *k*. Define *M* = 2^{m}. A vEB tree T over the universe {0, ..., *M*−1} has a root node that stores an array T.children of length √*M*. T.children[i] is a pointer to a vEB tree that is responsible for the values {*i*√*M*, ..., (*i*+1)√*M*−1}. Additionally, *T* stores two values T.min and T.max as well as an auxiliary vEB tree T.aux.

Data is stored in a vEB tree as follows: The smallest value currently in the tree is stored in T.min and largest value is stored in T.max. Note that T.min is not stored anywhere else in the vEB tree, while T.max is. If *T* is empty then we use the convention that T.max=−1 and T.min=M. Any other value *x* is stored in the subtree T.children[i] where *i* = ⌊*x*/√*M*⌋. The auxiliary tree T.aux keeps track of which children are non-empty, so T.aux contains the value *j* if and only if T.children[j] is non-empty.

### FindNext

The operation FindNext(T, x) that searches for the successor of an element *x* in a vEB tree proceeds as follows: If *x*<T.min then the search is complete, and the answer is T.min. If x≥T.max then the next element does not exist, return M. Otherwise, let *i* = *x*/√*M*. If x<T.children[i].max then the value being searched for is contained in T.children[i] so the search proceeds recursively in T.children[i]. Otherwise, we search for the value *i* in T.aux. This gives us the index *j* of the first subtree that contains an element larger than *x*. The algorithm then returns T.children[j].min. The element found on the children level needs to be composed with the high bits to form a complete next element.

functionFindNext(T, x).ifx < T.minthenreturnT.minifx ≥ T.maxthen// no next elementreturnM i = floor(x/√M) lo = x mod √Mhi = √MFindNext(T.aux, i)iflo < T.children[i].maxthenreturnhi + FindNext(T.children[i], lo)returnhi + T.children[FindNext(T.aux, i)].minend

Note that, in any case, the algorithm performs *O*(1) work and then possibly recurses on a subtree over a universe of size *M*^{1/2} (an *m*/2 bit universe). This gives a recurrence for the running time of , which resolves to *O*(log *m*) = *O*(log log *M*).

### Insert

The call insert(T, x) that inserts a value x into a vEB tree T operates as follows:

- If
*T*is empty then we set T.min = T.max = x and we are done. - Otherwise, if x<T.min then we insert T.min into the subtree i responsible for T.min and then set T.min = x. If T.children[i] was previously empty, then we also insert i into T.aux
- Otherwise, if x>T.max then we insert x into the subtree i responsible for x and then set T.max = x. If T.children[i] was previously empty, then we also insert i into T.aux
- Otherwise, T.min< x < T.max so we insert x into the subtree i responsible for x. If T.children[i] was previously empty, then we also insert i into T.aux.

In code:

functionInsert(T, x)ifT.min > T.maxthen// T is emptyT.min = T.max = x;returnifx < T.minthenswap(x, T.min)ifx > T.maxthenT.max = x i = floor(x / √M) lo = x mod √MInsert(T.children[i], lo)ifT.children[i].min == T.children[i].maxthenInsert(T.aux, i)end

The key to the efficiency of this procedure is that inserting an element into an empty vEB tree takes *O*(1) time. So, even though the algorithm sometimes makes two recursive calls, this only occurs when the first recursive call was into an empty subtree. This gives the same running time recurrence of as before.

### Delete

Deletion from vEB trees is the trickiest of the operations. The call Delete(T, x) that deletes a value *x* from a vEB tree T operates as follows:

- If T.min = T.max = x then
*x*is the only element stored in the tree and we set T.min = M and T.max = −1 to indicate that the tree is empty. - Otherwise, if x == T.min then we need to find the second-smallest value
*y*in the vEB tree, delete it from its current location, and set T.min=y. The second-smallest value*y*is T.children[T.aux.min].min, so it can be found in*O*(1) time. We delete*y*from the subtree that contains it. - If x≠T.min and x≠T.max then we delete x from the subtree T.children[i] that contains
*x*. - If x == T.max then we will need to find the second-largest value
*y*in the vEB tree and set T.max=y. We start by deleting x as in previous case. Then value*y*is either T.min or T.children[T.aux.max].max, so it can be found in*O*(1) time. - In any of the above cases, if we delete the last element
*x*or*y*from any subtree T.children[i] then we also delete*i*from T.aux

In code:

functionDelete(T, x)ifT.min == T.max == xthenT.min = M T.max = −1returnifx == T.minthenhi = T.aux.min * √Mj = T.aux.min T.min = x = hi + T.children[j].min i = floor(x / √M) lo = x mod √MDelete(T.children[i], lo)ifT.children[i] is emptythenDelete(T.aux, i)ifx == T.maxthenifT.aux is emptythenT.max = T.minelsehi = T.aux.max * √Mj = T.aux.max T.max = hi + T.children[j].maxend

Again, the efficiency of this procedure hinges on the fact that deleting from a vEB tree that contains only one element takes only constant time. In particular, the last line of code only executes if *x* was the only element in T.children[i] prior to the deletion.

### Discussion

The assumption that log *m* is an integer is unnecessary. The operations *x*/√*M* and *x* mod √*M* can be replaced by taking only higher-order ⌈*m*/2⌉ and the lower-order ⌊*m*/2⌋ bits of x, respectively. On any existing machine, this is more efficient than division or remainder computations.

The implementation described above uses pointers and occupies a total space of *O*(*M*) = *O*(2^{m}). This can be seen as follows. The recurrence is .
Resolving that would lead to .
One can, fortunately, also show that *S*(*M*) = *M*−2 by induction.[4]

In practical implementations, especially on machines with *shift-by-k* and *find first zero* instructions, performance can further be improved by switching to a bit array once m equal to the word size (or a small multiple thereof) is reached. Since all operations on a single word are constant time, this does not affect the asymptotic performance, but it does avoid the majority of the pointer storage and several pointer dereferences, achieving a significant practical savings in time and space with this trick.

An obvious optimization of vEB trees is to discard empty subtrees. This makes vEB trees quite compact when they contain many elements, because no subtrees are created until something needs to be added to them. Initially, each element added creates about log(*m*) new trees containing about *m*/2 pointers all together. As the tree grows, more and more subtrees are reused, especially the larger ones. In a full tree of 2^{m} elements, only O(2^{m}) space is used. Moreover, unlike a binary search tree, most of this space is being used to store data: even for billions of elements, the pointers in a full vEB tree number in the thousands.

However, for small trees the overhead associated with vEB trees is enormous: on the order of √*M*. This is one reason why they are not popular in practice. One way of addressing this limitation is to use only a fixed number of bits per level, which results in a trie. Alternatively, each table may be replaced by a hash table, reducing the space to *O*(*n* log *M*) (where n is the number of elements stored in the data structure) at the expense of making the data structure randomized. Other structures, including y-fast tries and x-fast tries have been proposed that have comparable update and query times and also use randomized hash tables to reduce the space to *O*(*n*) or *O*(*n* log *M*).

## References

- Peter van Emde Boas:
*Preserving order in a forest in less than logarithmic time*(*Proceedings of the 16th Annual Symposium on Foundations of Computer Science*10: 75-84, 1975) - Gudmund Skovbjerg Frandsen:
*Dynamic algorithms: Course notes on van Emde Boas trees (PDF)*(University of Aarhus, Department of Computer Science) - Thomas H. Cormen, Charles E. Leiserson, Ronald L. Rivest, and Clifford Stein.
*Introduction to Algorithms*, Third Edition. MIT Press, 2009. ISBN 978-0-262-53305-8. Chapter 20: The van Emde Boas tree, pp. 531–560. - Rex, A. "Determining the space complexity of van Emde Boas trees". Retrieved 2011-05-27.

### Further reading

- Erik Demaine, Sam Fingeret, Shravas Rao, Paul Christiano. Massachusetts Institute of Technology. 6.851: Advanced Data Structures (Spring 2012). Lecture 11 notes. March 22, 2012.
- van Emde Boas, P.; Kaas, R.; Zijlstra, E. (1976). "Design and implementation of an efficient priority queue".
*Mathematical Systems Theory*.**10**: 99–127. doi:10.1007/BF01683268.