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
The idea of saving how many results the index contains together with the index is a great idea! We already store the seq because we need to know when to update it, so it should be easy to add. Please note it is not count, its the size() function on the bitset. If you do a query on 3 parameters where you have an index of say the first, then you check how many results that have, and if its low enough you just filter directly instead of creating indexes for the other two as that is the slow part. What the threshold should be could probably be configured when loading jitdb, even better if it could be based on how many records can be read in 200ms or something like that.
The text was updated successfully, but these errors were encountered:
Forked from issue #5, from this comment.
The text was updated successfully, but these errors were encountered: