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.

Sign up for GitHub

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

Jump to bottom

Include some benchmarks... #2

Closed
lemire opened this issue Jul 17, 2013 · 0 comments
Closed

Include some benchmarks... #2

lemire opened this issue Jul 17, 2013 · 0 comments

Comments

@lemire
Copy link
Member

lemire commented Jul 17, 2013

Even if it is not perfect... try to include some benchmarks... For example, you could start by comparing the speed and memory usage of RoaringBitmap with the Java BitSet class.
@ghost ghost assigned samytto Jul 17, 2013
@lemire lemire closed this as completed Mar 3, 2014
lemire pushed a commit that referenced this issue Aug 29, 2017
@blacelle
Merge pull request #2 from RoaringBitmap/master
ccc2645 
Fixing support for select with very large bitmaps
marshallpierce referenced this issue in marshallpierce/RoaringBitmap Jun 7, 2019
@marshallpierce
Move the roaringbitmap subdir (and submodule) to RoaringBitmap.
aca1bd7 
This makes it possible to have the generated artifact have an artifact
id of RoaringBitmap *and* have inter-subproject dependencies be
consistent with the generated pom without doing any xml wrangling on
the generated poms.

(Attempt #2 -- first one dropped some test binary inpputs)
hn5092 referenced this issue in hn5092/RoaringBitmap Sep 4, 2019
@hn5092
Kyligence#2 revert Kyligence#1
764ce4f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lemire @samytto