-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Chunk based iteration in accumulate_indices
#13451
Conversation
Signed-off-by: Jay Zhan <[email protected]>
Signed-off-by: Jay Zhan <[email protected]>
Signed-off-by: Jay Zhan <[email protected]>
let bit_chunks = filter.values().bit_chunks(); | ||
let group_indices_remainder = group_indices_chunks.remainder(); | ||
|
||
group_indices_chunks.zip(bit_chunks.iter()).for_each( |
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.
I'm wondering if just using set_indices
here is possible to iterate on valid indices?
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.
I'm quite surprise that the fixed chunk size (64) is faster than iterating set_indices
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.
Yeah it seems it is faster (generating faster code) when valid values are high enough.
Signed-off-by: Jay Zhan <[email protected]>
Signed-off-by: Jay Zhan <[email protected]>
accumulate_indices
accumulate_indices
|
Signed-off-by: Jay Zhan <[email protected]>
I wonder if any of the queries in that benchmark uses aggregate filters? |
Neither Q7, Q10, nor Q24 uses an aggregate filter. |
Can we maybe find / create a query with filter? Maybe add one in |
aggregate filter required postgres dialect, it might be easier to run benchmark with criterion |
Signed-off-by: jayzhan211 <[email protected]>
Signed-off-by: jayzhan211 <[email protected]>
Signed-off-by: jayzhan211 <[email protected]>
Signed-off-by: jayzhan211 <[email protected]>
Signed-off-by: jayzhan211 <[email protected]>
@Dandandan PTAL |
Thanks @Dandandan |
Which issue does this PR close?
Closes #.
Rationale for this change
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?