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
[Java] Optimize bit operations performance #19814
Comments
Animesh Trivedi / @animeshtrivedi:
I can open a pull request for the first two items. |
Wes McKinney / @wesm: |
Animesh Trivedi / @animeshtrivedi: |
Wes McKinney / @wesm: |
Azim Afroozeh: I'm opening the following pull request for this issue: #5930 This patch does the following changes:
|
Todd Farmer / @toddfarmer: |
From @animeshtrivedi's benchmark finding:
Materialize values from Validity and Value direct buffers instead of
calling getInt() function on the IntVector. This is implemented as a new
Unsafe reader type (
https://github.com/animeshtrivedi/benchmarking-arrow/blob/master/src/main/java/com/github/animeshtrivedi/benchmark/ArrowReaderUnsafe.java#L31
)
Optimize bitmap operation to check if a bit is set or not (
https://github.com/animeshtrivedi/benchmarking-arrow/blob/master/src/main/java/com/github/animeshtrivedi/benchmark/ArrowReaderUnsafe.java#L23
)
Reporter: Li Jin / @icexelloss
Subtasks:
PRs and other links:
Note: This issue was originally created as ARROW-3495. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: