<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Better bitmap performance with Roaring bitmaps · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1402.6407/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1402.6407/feed.xml" rel="self" type="application/rss+xml" /><item><title>Better bitmap performance with Roaring bitmaps — mentioned by kuwze</title><link>https://news.ycombinator.com/item?id=18157556</link><guid isPermaLink="false">urn:hackerpapers:mention:1402.6407:18157556</guid><pubDate>Sat, 06 Oct 2018 22:08:49 GMT</pubDate><description>&lt;p&gt;Edit: I misspoke. It seems that they did a very thorough comparison with Word Aligned Hybrid compression scheme. I was just searching the PDFs for &amp;#x27;fastbit&amp;#x27;. Past discussion of Roaring bitmaps[0]. I find it interesting that there is no real comparison (at least under the publications at the home page[1]) between Roaring bitmaps and FastBit[2] except for this little quote from &amp;#x27;Better bitmap performance with Roaring bitmaps&amp;#x27; [3]: Our approach is reminiscent of O’Neil and O’Neil’s RIDBit external-memory system. RIDBit is a B-tree of bitmaps, where a list is used instead when a chunk’s density…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1402.6407/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DB</category></item><item><title>Better bitmap performance with Roaring bitmaps — mentioned by willglynn</title><link>https://news.ycombinator.com/item?id=15903144</link><guid isPermaLink="false">urn:hackerpapers:mention:1402.6407:15903144</guid><pubDate>Tue, 12 Dec 2017 05:10:56 GMT</pubDate><description>&lt;p&gt;There are a lot of tools available in the &amp;quot;compressed bitmap&amp;quot; space. When last I needed something like this, I evaluated several approaches and ended up selecting Roaring Bitmaps: https://arxiv.org/abs/1402.6407 http://roaringbitmap.org That application had some particular wins relating to large sparse bitmaps, especially the ability to efficiently perform binary operations directly on their compressed representations. I didn&amp;#x27;t need random insertions, so this ended up being a win across the board: faster runtime, lower memory footprint, and lower I/O requirements versus a normal bitset.&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1402.6407/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DB</category></item></channel></rss>
