Skip to content

Lazy ScalarFn::validity - #9932

Draft
myrrc wants to merge 3 commits into
developfrom
myrrc/lazy-scalarfn-validity
Draft

myrrc wants to merge 3 commits into
developfrom
myrrc/lazy-scalarfn-validity

Conversation

@myrrc

@myrrc myrrc commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

TODO

@myrrc myrrc added the changelog/feature A new feature label Sep 17, 2026
@codspeed

codspeed Bot commented Sep 17, 2026

Copy link
Copy Markdown

Merging this PR will degrade performance by 15.92%

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

⚡ 1 improved benchmark
❌ 2 regressed benchmarks
✅ 216 untouched benchmarks
⏩ 2252 skipped benchmarks1

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Benchmark BASE HEAD Efficiency
arrow_checked_add_u32_neon[16384] 12.4 µs 20.4 µs -39.29%
filtered_owned_i64_avx2[OneNullInEight] 22.5 µs 25.6 µs -12.29%
mul_i32_nonnull_avx512 7.9 µs 7.1 µs +11.61%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.


Comparing myrrc/lazy-scalarfn-validity (4ca7b44) with develop (895935e)

Open in CodSpeed

Footnotes

  1. 2252 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports.

Signed-off-by: Mikhail Kot <mikhail@spiraldb.com>
Signed-off-by: Mikhail Kot <mikhail@spiraldb.com>
@myrrc
myrrc force-pushed the myrrc/lazy-scalarfn-validity branch from 93069bc to 4ca7b44 Compare September 21, 2026 11:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog/feature A new feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant