k
is a key store B+treev
is a key-value store B+treei
is an index based B+trees
is an stack/queue based B+tree
These are from the help of @trincot on StackOverflow. Used as a reference implementation for various B+trees, with the added constraint that all arrays are powers of two sized, to optimize for memory layout.
Goal would be, in a multithreaded environment, to make this work with concurrent B+trees like PALM: Parallel Architecture-Friendly Latch-Free Modifications to B+ Trees on Many-Core Processors.