-
Notifications
You must be signed in to change notification settings - Fork 53
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
simdcomp vs roaringBitmap #22
Comments
Thanks. I don't think that it is comparable, at all. The simdcomp library is a low level library that supports some algorithms, but it does not provide an integrated data structure. It is up to you to build up a format, data structure. Roaring bitmaps are a standard format, a set of data structures and so forth. If you are interested in something like variable-length coding, I suggest you look up the streamvbyte library instead. |
Thanks for the quick reply, one more doubt. I was checking simdcomp as it was doing very well against all others, (sorry, as there are many materials out there, i may not be looking in the right order too) |
You have looked at No doubt? I am not sure I know what you mean by "a sample".
Please refer to https://github.com/lemire/streamvbyte and the paper at https://arxiv.org/abs/1709.08990 Stream VByte is extremely fast. I don't think that there is any byte-oriented codec out there that can match it. |
Thats cool, |
I was playing with a few benchmark tests like below. (exploring cgo, so might be not the right way/ some mistakes there) go test -benchmem -bench=. code
|
Pull requests are invited!!! It is a great idea to provide more examples, but I simply can't do it all... I rely on people like you to help out. |
@lemire , thanks a lot for these wonderful libraries.
Just being curious about one thing here, how do these two libraries (simdcomp vs roaringBitmap) stand against each other in terms of encoding/decoding speed and compression performances when it comes to ordered numbers?
Though i have used roaringBitmaps, never benchmarked/verified the compression ratio there..
But while glancing over this simdcomp, end up running the go/test and realised that the compression ratio was ~32.
Another side note, is it would be great to have a sample for the variable length array encoding/decoding for the Go users in simdcomp.
thanks!
The text was updated successfully, but these errors were encountered: