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
Ran parts of some benchmarks and found that it generally helps for the LMDB store, but can make things worse for the MemoryStore. Kinda makes sense since the MemoryStore has a very accurate statistics.
It tries to estimate the cardinality based on the distance between the keys. For the first n keys the distance between two consecutive ones is measured.
Then more samples are taken, e.g., in the middle of the existing key range and in the end.
Finally, based on the computed distance between to keys an estimation is computed.
(Sounds a bit complicated. Maybe I need to create a formula for this ;-))
BTW, libmdbx - a fork of LMDB has something like the NativeStore's btree estimation of nodes built-in.
What happens if you don't have a perfect match for the index? Does it account for the fact that a lot of results will be discarded very quickly?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
GitHub issue resolved: #5672
Briefly describe the changes proposed in this PR:
PR Author Checklist (see the contributor guidelines for more details):
mvn process-resourcesto format from the command line)