Re:A Comparison of Log-Structured Merge (LSM) and Fractal Tr...
by thorwahnawa on Sunday March 22, 2015 @08:40PM
(#9248882)
Yes. You can grab the ancestors shared and the leaf or subtree you want to modify exclusive. If all of your writers land in the root of the tree because it's a small tree, they all contend on the same lock.
[ Parent
| on HN ]
Re:A Comparison of Log-Structured Merge (LSM) and Fractal Tr...
by skybrian on Sunday March 22, 2015 @09:07PM
(#9248948)
I'm no expert, but it seems like you need to guess at some key ranges and start the BTree at some minimum size even if most of the leaves start out empty. Either that, or don't write anything until the tree grows a bit and rely on a writeahead log for durability.
Hotspots could still show up further down, though, if writes aren't fairly random.
Re:A Comparison of Log-Structured Merge (LSM) and Fractal Tr...
by koverstreet on Sunday March 22, 2015 @09:14PM
(#9248966)
So it's only an issue with small trees? I'm not really seeing the issue then, use smaller btree nodes if it's really an issue...
Re:A Comparison of Log-Structured Merge (LSM) and Fractal Tr...
by dignati on Monday March 23, 2015 @05:58AM
(#9250104)
The issue seems yo be that writes in Fractal trees always go through the root node. This would lead to a situation similar to small B-Trees where writes will most likely access the root node and contend.