Conversation
|
run benchmark filter_kernels boolean_kernels arrow_reader arrow_reader_clickbench |
|
🤖 Hi @Dandandan, thanks for the request (#9284 (comment)).
Please choose one or more of these with |
|
🤖 |
|
🤖: Benchmark completed Details
|
|
🤖 |
|
🤖: Benchmark completed Details
|
|
🤖 |
|
🤖: Benchmark completed Details
|
|
🤖 |
|
🤖: Benchmark completed Details
|
|
run benchmark boolean_kernels filter_kernels |
|
🤖 |
|
🤖: Benchmark completed Details
|
|
🤖 |
|
🤖: Benchmark completed Details
|
|
run benchmark boolean_kernels |
|
🤖 |
|
🤖: Benchmark completed Details
|
|
run benchmark boolean_kernels |
|
🤖 |
|
🤖: Benchmark completed Details
|
|
run benchmark boolean_kernels |
|
run benchmark boolean_kernels |
1 similar comment
|
run benchmark boolean_kernels |
|
🤖 |
|
(sorry runner had been restarted for some reason) |
|
🤖: Benchmark completed Details
|
|
run benchmark filter_kernels |
|
run benchmark arrow_reader_clickbench |
|
🤖 |
|
🤖: Benchmark completed Details
|
|
🤖 |
|
run benchmark coalesce_kernels |
|
🤖: Benchmark completed Details
|
|
🤖 |
|
🤖: Benchmark completed Details
|
|
Those are some impressive benchmark results |
Which issue does this PR close?
Rationale for this change
We can speed up bitwise operations (and / or / etc) on boolean data containing offsets.
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?