-
Notifications
You must be signed in to change notification settings - Fork 583
some initial Roaring64Bitmap benchmarks #797
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
Conversation
| public Roaring64Bitmap addLong(BenchmarkState state) { | ||
| Roaring64Bitmap bitmap = new Roaring64Bitmap(); | ||
| for (long index : state.indexes) { | ||
| bitmap.addLong(index); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are alternatives worth including: Roaring64Bitmap.bitmapOf (it calls the bulked add function underneath). It should run at the same speed (just about) since we have not optimized it, but it has the potential to be optimized dramatically.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added some more methods and patterns
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
were there the ones that you wanted
|
Please consider my small comment. |
|
from the command line JMH ignores the annotations that control the benchmark (time, iterations, warmups, forks) e.g. from |
|
@mkeskells JMH is the de facto standard for running benchmarks in Java, but it has downsides. |
|
Merged. |
SUMMARY
no changes to code or unit test. Just benchmarks for addition and lookup
Automated Checks
./gradlew testand made sure that my PR does not break any unit test.