-
Notifications
You must be signed in to change notification settings - Fork 111
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
Really high false negative rate in ScalableCuckooFilter #50
Comments
I think this happens because during Delete, it tries to remove the element from all the children, and accidentally remove the footprint of other elements in these children
|
https://cis.temple.edu/~wu/research/publications/Publication_files/Chen_ICNP_2017.pdf According to the section "ReliableDelete" the fingerprint computation across children filter should be the same, but this is not the case
Each time a new filter is created, bucketPow changes |
If i make the scaleFactor to remain the same size as the previous filter, the test mentioned in this issue passes |
But after adding this, the false positive rate also increases, which is also mentioned by the paper (false positive correlates with the count of the children bloom filter and fingerprint size) I'm also opening a PR to this fork: https://github.com/panmari/cuckoofilter, which has large fingerprint size and provide more reliable FP rate. |
The feature of having a scalable cuckooFilter is really convenient but for my usecase the application cannot tolerate false negative.
To reproduce
And the result
The text was updated successfully, but these errors were encountered: