You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Meaning a more cache-line friendly variant for a static balanced binary search tree (RedBlack tree). Usually you'd use an array representation...
As an alternative to storing this search tree structure for our secondary indexes in our trie (the RedBlack tree nodes are stored in the leaf nodes of our tries) and fully reconstructing it in memory, we could add a persistent adaptive radix trie that replaces the trie and the RedBlack tree. The adaptive radix trie (ART) should be versioned in the same manner as our main document trie.
The text was updated successfully, but these errors were encountered:
Maybe I had a crazy thought. Would it make sense to store and update a redblack tree in the single read-write trx per resource, but for read-only trx simply use another cache-friendly index structure and to build this structure from the stored redblack tree? Maybe reconstruction would be costly, hmm
Meaning a more cache-line friendly variant for a static balanced binary search tree (RedBlack tree). Usually you'd use an array representation...
As an alternative to storing this search tree structure for our secondary indexes in our trie (the RedBlack tree nodes are stored in the leaf nodes of our tries) and fully reconstructing it in memory, we could add a persistent adaptive radix trie that replaces the trie and the RedBlack tree. The adaptive radix trie (ART) should be versioned in the same manner as our main document trie.
The text was updated successfully, but these errors were encountered: