Fractal tree index  

Type  tree  
Invented  2007  
Invented by  Michael A. Bender, Martin FarachColton, Bradley C. Kuszmaul  
Time complexity in big O notation  

In computer science, a fractal tree index is a tree data structure that keeps data sorted and allows searches and sequential access in the same time as a Btree but with insertions and deletions that are asymptotically faster than a Btree. Like a Btree, a fractal tree index is a generalization of a binary search tree in that a node can have more than two children. Furthermore, unlike a Btree, a fractal tree index has buffers at each node, which allow insertions, deletions and other changes to be stored in intermediate locations. The goal of the buffers is to schedule disk writes so that each write performs a large amount of useful work, thereby avoiding the worstcase performance of Btrees, in which each disk write may change a small amount of data on disk. Like a Btree, fractal tree indexes are optimized for systems that read and write large blocks of data. The fractal tree index has been commercialized in databases by Tokutek. Originally, it was implemented as a cacheoblivious lookahead array,^{[1]} but the current implementation is an extension of the B^{ε} tree.^{[2]} The B^{ε} is related to the Buffered Repository Tree.^{[3]} The Buffered Repository Tree has degree 2, whereas the B^{ε} tree has degree B^{ε}. The fractal tree index has also been used in a prototype filesystem.^{[4]}^{[5]} An open source implementation of the fractal tree index is available,^{[6]} which demonstrates the implementation details outlined below.
In fractal tree indexes, internal (nonleaf) nodes can have a variable number of child nodes within some predefined range. When data is inserted or removed from a node, its number of child nodes changes. In order to maintain the predefined range, internal nodes may be joined or split. Each internal node of a Btree will contain a number of keys that is one less than its branching factor. The keys act as separation values which divide its subtrees. Keys in subtrees are stored in search tree order, that is, all keys in a subtree are between the two bracketing values. In this regard, they are just like Btrees.
Fractal tree indexes and Btrees both exploit the fact that when a node is fetched from storage, a block of memory, whose size is denoted by , is fetched. Thus, nodes are tuned to be of size approximately . Since access to storage can dominate the running time of a data structure, the timecomplexity of external memory algorithms is dominated by the number of read/writes a data structure induces. (See, e.g.,^{[7]} for the following analyses.)
In a Btree, this means that the number of keys in a node is targeted to be enough to fill the node, with some variability for node splits and merges. For the purposes of theoretical analysis, if keys fit in a node, then the tree has depth , and this is the I/O complexity of both searches and insertions.
Fractal trees nodes use a smaller branching factor, say, of . The depth of the tree is then , thereby matching the Btree asymptotically. The remaining space in each node is used to buffer insertions, deletion and updates, which we refer to in aggregate as messages. When a buffer is full, it is flushed to the children in bulk. There are several choices for how the buffers are flushed, all leading to similar I/O complexity. Each message in a node buffer will be flushed to a particular child, as determined by its key. Suppose, for concreteness, that messages are flushed that are heading to the same child, and that among the children, we pick the one with the most messages. Then there are at least messages that can be flushed to the child. Each flush requires flushes, and therefore the permessage cost of a flush is .
Consider the cost of an insertion. Each message gets flushed times, and the cost of a flush is . Therefore, the cost of an insertion is . Finally, note that the branching factor can vary, but for any branching factor , the cost of a flush is , thereby providing a smooth tradeoff between search cost, which depends on the depth of the search tree, and therefore the branching factor, versus the insertion time, which depends on the depth of the tree but more sensitively on the size of the buffer flushes.
This section compares fractal tree indexes with other external memory indexing data structures. The theoretical literature on this topic is very large, so this discussion is limited to a comparison with popular data structures that are in use in databases and file systems.
The search time of a Btree is asymptotically the same as that of a fractal tree index. However, a fractal tree index has deeper trees than a Btree, and if each node were to require an I/O, say if the cache is cold, then a fractal tree index would induce more IO. However, for many workloads most or all internal nodes of both Btrees and fractal tree indexes are already cached in RAM. In this case, the cost of a search is dominated by the cost of fetching the leaf, which is the same in both cases. Thus, for many workloads, fractal tree indexes can match Btrees in terms of search time.
Where they differ is on insertions, deletions and updates. An insertion in a fractal tree index takes whereas Btrees require . Thus, fractal tree indexes are faster than Btrees by a factor of . Since can be quite large, this yields a potential twoorderofmagnitude improvement in worstcase insertion times, which is observed in practice. Both Btrees and fractal tree indexes can perform insertions faster in the best case. For example, if keys are inserted in sequential order, both data structures achieve a I/Os per insertion. Thus, because the best and worst cases of Btrees differ so widely, whereas fractal tree indexes are always near their best case, the actual speedup that fractal tree indexes achieve over Btrees depends on the details of the workload.
Logstructured mergetrees (LSMs) refer to a class of data structures which consists of two or more index structures of exponentially growing capacities. When a tree at some level reaches its capacity, it is merged into the next bigger level. The IOcomplexity of an LSM depends on parameters such as the growth factor between levels and the data structure chosen at each level, so in order to analyze the complexity of LSMs, we need to pick a specific version. For comparison purposes, we select the version of LSMs that match fractal tree indexes on insertion performance.
Suppose an LSM is implemented via Btrees, each of which has a capacity that is larger than its predecessor. The merge time depends on three facts: The sorted order of keys in an item Btree can be produced in IOs; Two sorted lists of and items can be merged into a sorted list in IOs; and a Btree of a sorted list of items can be built in IOs. When a tree overflows, it is merged into a tree whose size is larger, therefore a level that holds items requires IOs to merge. An item may be merged once per level, giving a total time of , which matches the fractal tree index.
The query time is simply the Btree query time at each level. The query time into the ^{th} level is , since the ^{th} level has capacity . The total time is therefore . This is larger than both the Btree and fractal tree indexes by a logarithmic factor. In fact, although Btrees and fractal tree indexes are both on the optimal tradeoff curve between insertions and queries, LSMs are not. They are incomparable with Btrees and are dominated by fractal tree indexes.
A few notes about LSMs: there are ways to make the queries faster. For example, if only membership queries are required and no successor/predecessor/range queries are, then Bloom filters can be used to speed up queries. Also, the growth factor between levels can be set to some other value, giving a range of insertion/query tradeoffs. However, for every choice of insertion rate, the corresponding fractal tree index has faster queries.
The fractal tree index is a refinement of the B^{ε} tree. Like a B^{ε} tree, it consists of nodes with keys and buffers and realizes the optimal insertion/query tradeoff. The fractal tree index differs in including performance optimization and in extending the functionality. Examples of improved functionality include ACID semantics. Btree implementations of ACID semantics typically involve locking rows that are involved in an active transactions. Such a scheme works well in a Btree because both insertions and queries involve fetching the same leaf into memory. Thus, locking an inserted row does not incur an IO penalty. However, in fractal tree indexes, insertions are messages, and a row may reside in more than one node at the same time. Fractal tree indexes therefore require a separate locking structure that is IOefficient or resides in memory in order to implement the locking involved in implementing ACID semantics.
Fractal tree indexes also have several performance optimizations. First, buffers are themselves indexed in order to speed up searches. Second, leaves are much larger than in Btrees, which allows for greater compression. In fact, the leaves are chosen to be large enough that their access time is dominated by the bandwidth time, and therefore amortizes away the seek and rotational latency. Large leaves are an advantage with large range queries but slow down point queries, which require accessing a small portion of the leaf. The solution implemented in fractal tree indexes is to have large leaves that can be fetched as a whole for fast range queries but are broken into smaller pieces call basement nodes which can be fetched individually. Accessing a basement node is faster than accessing a leaf, because of the reduced bandwidth time. Thus the substructure of leaves in fractal tree indexes, as compared to B^{ε} trees allows both range and point queries to be fast.
Insertions, deletions and updates are inserted as message into buffers that make their way towards the leaves. The messaging infrastructure can be exploited to implement a variety of other operations, some of which are discussed below.
An upsert is a statement that inserts a row if it does not exist and updates it if it does. In a Btree, an upsert is implemented by first searching for the row and then implementing an insertion or an update, depending on the result of the search. This requires fetching the row into memory if it is not already cached. A fractal tree index can implement an upsert by inserting a special upsert message. Such a message can, in theory, implement arbitrary pieces of code during the update. In practice, four update operations are supported:
These correspond to the update operations used in LinkBench,^{[8]} a benchmark proposed by Facebook. By avoiding the initial search, upsert messages can improve the speed of upserts by orders of magnitude.
So far, all message types have modified single rows. However, broadcast messages, which are copied to all outgoing buffers, can modify all rows in a database. For example, broadcast messages can be used to change the format of all rows in a database. Although the total work required to change all rows is unchanged over the bruteforce method of traversing the table, the latency is improved, since, once the message is injected into the root buffer, all subsequent queries will be able to apply the schema modification to any rows they encounter. The schema change is immediate and the work is deferred to such a time when buffers overflow and leaves would have gotten updated anyway.
The fractal tree index has been implemented and commercialized by Tokutek. It is available as TokuDB as a storage engine for MySQL and MariaDB, and as TokuMX, a more complete integration with MongoDB. Fractal tree indexes have also been used in prototype filesystems, TokuFS^{[4]} and BetrFS.^{[5]}