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

Calculations for optimalEntriesPerBucket and optimalLoadFactor #1

Open
bdupras opened this issue Dec 8, 2015 · 2 comments
Open

Calculations for optimalEntriesPerBucket and optimalLoadFactor #1

bdupras opened this issue Dec 8, 2015 · 2 comments

Comments

@bdupras
Copy link
Owner

bdupras commented Dec 8, 2015

The current methods for determining bucket size (number of entries per bucket) and load factor are based on prose in section 5.1 of Cuckoo Filter: Practically Better Than Bloom.

It would be better to have true calculations instead of the current conditional logic with hard-coded values.

Heya @apc999 - do you have any recommendations here?

// cc @beala

@bdupras
Copy link
Owner Author

bdupras commented Dec 8, 2015

Oh - and by the way, this is work in progress. This version of the CuckooFilter doesn't yet function. When I get it functional (soon), I'll probably break it out from the guava fork into its own repo.

@apc999
Copy link
Collaborator

apc999 commented Dec 9, 2015

@bdupras , my past experience is 4 cells per bucket ensures pretty good load factor --- which is 95%+ with 500 retries on insert; Using 8 cells per bucket will get even higher load factor (e.g., close to 99%) with even less retires, but at the cost of doubling the false positive rate. I would say 4 or 8 is a good value to use in practice

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants