Estimating size required for memory mapped boost rtree
问题 We have a scenario where we dynamically grow a memory mapped file used for boost's r-tree geometric index. We also make use of boost's interprocess memory mapped file api's. Mechanics are already sorted out in terms of unmapping the file, growing, and remapping - this all works. Thus far we've tried overestimating the size with a factor 10 of the inherent size of our coordinates, which works but is grossly over-estimated when inspecting with du . Is there some way to predict (worst-case or