Alamb/test boolean kernels

[alamb]

Which issue does this PR close?

We generally require a GitHub issue to be filed for all bug fixes and enhancements and this helps us generate change logs for our releases. You can link an issue to this PR using the GitHub syntax.

• Closes #NNN.

Rationale for this change

• Similarly to TESTING: Change `BooleanBuffer::append_packed_range to use bitwise_binary_op  #8744

What changes are included in this PR?

• Apply feat: add apply_unary_op and apply_binary_op bitwise operations #8619 to the existing boolean kernels

benchmark results for boolean_kernels

Are these changes tested?

will benchmark
If tests are not included in your PR, please explain why (for example, are they covered by existing tests)?

Are there any user-facing changes?

If there are user-facing changes then we may require documentation to be updated before approving the PR.

If there are any breaking changes to public APIs, please call them out.

[alamb]

🤖 ./gh_compare_arrow.sh Benchmark Script Running
Linux aal-dev 6.14.0-1018-gcp #19~24.04.1-Ubuntu SMP Wed Sep 24 23:23:09 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
Comparing alamb/test_boolean_kernels (b0cf38b) to eaca232 diff
BENCH_NAME=boolean_kernels
BENCH_COMMAND=cargo bench --features=arrow,async,test_common,experimental --bench boolean_kernels
BENCH_FILTER=
BENCH_BRANCH_NAME=alamb_test_boolean_kernels
Results will be posted here when complete

[alamb]

🤖: Benchmark completed

Details

group         alamb_test_boolean_kernels             main
-----         --------------------------             ----
and           1.00    265.0±0.39ns        ? ?/sec    1.05    278.3±1.44ns        ? ?/sec
and_sliced    1.00    254.0±0.36ns        ? ?/sec    4.84   1228.2±2.47ns        ? ?/sec
not           1.00    189.4±0.31ns        ? ?/sec    1.13    214.3±1.98ns        ? ?/sec
not_sliced    1.00    592.5±0.89ns        ? ?/sec    1.18    697.8±1.35ns        ? ?/sec
or            1.13    282.5±1.07ns        ? ?/sec    1.00    251.1±2.04ns        ? ?/sec
or_sliced     1.00    284.1±0.75ns        ? ?/sec    3.85   1093.3±2.06ns        ? ?/sec

[alamb]

🤖 ./gh_compare_arrow.sh Benchmark Script Running
Linux aal-dev 6.14.0-1018-gcp #19~24.04.1-Ubuntu SMP Wed Sep 24 23:23:09 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
Comparing alamb/test_boolean_kernels (b0cf38b) to eaca232 diff
BENCH_NAME=boolean_kernels
BENCH_COMMAND=cargo bench --features=arrow,async,test_common,experimental --bench boolean_kernels
BENCH_FILTER=
BENCH_BRANCH_NAME=alamb_test_boolean_kernels
Results will be posted here when complete

[alamb]

🤖: Benchmark completed

Details

group         alamb_test_boolean_kernels             main
-----         --------------------------             ----
and           1.00    265.1±0.42ns        ? ?/sec    1.03    273.9±1.28ns        ? ?/sec
and_sliced    1.00    254.3±0.92ns        ? ?/sec    4.83   1227.1±3.82ns        ? ?/sec
not           1.00    191.2±0.29ns        ? ?/sec    1.13    216.3±0.32ns        ? ?/sec
not_sliced    1.00    593.1±1.10ns        ? ?/sec    1.18    697.8±0.98ns        ? ?/sec
or            1.12    282.2±0.59ns        ? ?/sec    1.00    251.6±0.56ns        ? ?/sec
or_sliced     1.00    284.2±0.68ns        ? ?/sec    3.84   1092.4±1.87ns        ? ?/sec

[alamb]

That is interesting that OR is slower