We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently we are using a tree, but in theory, if it's compact enough, we could use a deletable bloom filter.
One of the biggest advantage is the fact that we can avoid to iterate over the keys during the table stats and sync process.
Obviously we need to check that the memory consumption of the structure is small enough.
Paper: http://arxiv.org/pdf/1005.0352.pdf
The text was updated successfully, but these errors were encountered:
looks like we have something like 100kb of supporting structure, may be a little bit too much (?)
Sorry, something went wrong.
No branches or pull requests
Currently we are using a tree, but in theory, if it's compact enough, we could use a deletable bloom filter.
One of the biggest advantage is the fact that we can avoid to iterate over the keys during the table stats and sync process.
Obviously we need to check that the memory consumption of the structure is small enough.
Paper: http://arxiv.org/pdf/1005.0352.pdf
The text was updated successfully, but these errors were encountered: