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

Consider roaring bitmaps #116

Open
staltz opened this issue Feb 8, 2021 · 3 comments
Open

Consider roaring bitmaps #116

staltz opened this issue Feb 8, 2021 · 3 comments

Comments

@staltz
Copy link
Member

staltz commented Feb 8, 2021

They seem faster than TypedFastBitSet (according to TypedFastBitSet's own benchmarks) but roaring is a native node module (probably won't run in the browser).

Also see https://www.npmjs.com/package/bitfield-db by substack

@arj03
Copy link
Member

arj03 commented Feb 8, 2021

Yes exactly, the non-browser part is why I didn't want to use them. Also it seems that the bitmap operation is not the part that takes up most of the time.

@staltz
Copy link
Member Author

staltz commented Feb 8, 2021

I thought so, I just wanted to track the comments I got here https://twitter.com/megaflop/status/1358771343047671810

@Barbarrosa
Copy link
Contributor

Barbarrosa commented Apr 25, 2021

@arj03 @staltz Looks like there's a WebAssembly port, i.e. roaring-wasm. I'm not sure how usable that is in the browser (esp. b/c it was made for AWS Lambda), but it may be worth a look.

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

3 participants