You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem/use-case that the feature addresses
I want store large number of user id whitelist (10,000,000 ~ 50,000,000 ) with using bitmap and the max value of the user ID will be 2,147,483,647.
If there is only 1 user in the bitmap and the value is 2,147,483,647, it will spend around 320MB memory.
If we can use some compression technology to reduce memory usage without affecting performance or even improve some performance, I think that would definitely be a great thing.
Maybe roaring bitmap is good choose to do some improvement.
Description of the feature
Support Roaring Bitmaps with new Commands
Alternatives you've considered
Support Roaring Bitmaps with existing bitmap commands if bitmap_engine="roaring" in config file.
bitmap_engine="string" as the default config to keep existing behavior.
The problem/use-case that the feature addresses
I want store large number of user id whitelist (10,000,000 ~ 50,000,000 ) with using bitmap and the max value of the user ID will be 2,147,483,647.
If there is only 1 user in the bitmap and the value is 2,147,483,647, it will spend around 320MB memory.
If we can use some compression technology to reduce memory usage without affecting performance or even improve some performance, I think that would definitely be a great thing.
Maybe roaring bitmap is good choose to do some improvement.
Description of the feature
Support Roaring Bitmaps with new Commands
Alternatives you've considered
Support Roaring Bitmaps with existing bitmap commands if bitmap_engine="roaring" in config file.
bitmap_engine="string" as the default config to keep existing behavior.
Additional information
About Roaring Bitmap
https://roaringbitmap.org/
https://github.com/RoaringBitmap/CRoaring
Some implementations from others
https://github.com/aviggiano/redis-roaring
The text was updated successfully, but these errors were encountered: