Redis 8.12-rc1's roaring bitmap type shrinks a sparse bitmap from 24MB to 239KB

7.7 relevance

Redis roaring bitmap benchmark with concrete numbers is highly technical and actionable.

General dev.to

Answer the board on AI readiness

Arrive with evidence, not opinion. See how your foundation benchmarks against your peers, get a clear read, and leave with a ranked place to start.

Why It Matters

For platform engineers managing high-cardinality user/event bitmaps in Redis, this offers an order-of-magnitude memory and throughput improvement for sparse workloads, but requires careful type migration and pre-release version-string quirks (reports as 8.11.240).

Key Takeaways

Evaluate your bitmap sparsity before enabling bitmap-default-roaring; use BITRANGEINTARRAY for efficient set-bit iteration, but avoid relying on pre-release version strings for automation.

Redis 8.12-rc1's roaring bitmap type shrinks a sparse bitmap from 24MB to 239KB

Summary

Redis 8.12-rc1 integrates redis-roaring as an opt-in bitmap type, shrinking a 200M-bit sparse bitmap from 25MB to 239KB and accelerating BITCOUNT 14x. The new BITRANGEINTARRAY command reads set-bit positions directly. However, the feature is a separate type (not a string encoding), so string commands like GETRANGE fail, and dense bitmaps see a ~1% memory regression.

Author

Alex Georgiev