-
Notifications
You must be signed in to change notification settings - Fork 19
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
Migrate Bitsets to Roaring Bitsets #363
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we use
bitset_core
for our bitsets, but I believe we could benefit in terms of performance and memory usage by using theroaring
crate, which uses compressed bitsets. Being that our bitsets are, in most cases, extremely sparse, I think this could really help.Eventually we probably want to do even better by moving to something like linked list storage instead of using bitsets and sparse vectors, but switching to roaring bitmaps should be a very easy change that could get us a lot of improvement.
We should see if we can profile Jumpy to see if there is any noticeable change in performance after the change. Even if it doesn't make it any faster, it should use up a lot less memory, which is a win as long as it isn't somehow slower.
The text was updated successfully, but these errors were encountered: