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

Allocate keys into off-heap memory #16

Open
dgrnbrg opened this issue Dec 24, 2013 · 2 comments
Open

Allocate keys into off-heap memory #16

dgrnbrg opened this issue Dec 24, 2013 · 2 comments

Comments

@dgrnbrg
Copy link
Contributor

dgrnbrg commented Dec 24, 2013

Keys are never GCed (although they can be in certain occaisions).

It'd be better to store just hashes in the chm, and do the collision detection/chaining off-heap.

@dgrnbrg
Copy link
Contributor Author

dgrnbrg commented Jan 18, 2014

This will be easy to implement once #15 is done.

@dgrnbrg
Copy link
Contributor Author

dgrnbrg commented Jan 27, 2014

The key to this implementation is that BinaryKey must have 2 constructors: a direct and a nondirect one. The direct one should be used on inserts into the hashtable, and the nondirect one for comparisons. In order to facilitate reuse of direct buffers, every put must first try to reuse the existing equivalent direct buffer already in the chm.

@dgrnbrg dgrnbrg modified the milestones: v4, v3 Feb 3, 2014
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

1 participant