Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't save index if it's small enough #8

Open
staltz opened this issue Nov 11, 2020 · 0 comments
Open

Don't save index if it's small enough #8

staltz opened this issue Nov 11, 2020 · 0 comments
Labels
idea / experiment Good for newcomers

Comments

@staltz
Copy link
Member

staltz commented Nov 11, 2020

Forked from issue #5, from this comment.

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.

@staltz staltz changed the title Save how many results the index contains together with the index Don't save index if it's small enough Dec 15, 2020
@staltz staltz added the idea / experiment Good for newcomers label Dec 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
idea / experiment Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant