Repository navigation
Attach RowFn validity directly to canonical output - #10742
1 benchmark regressed
3 warnings, 1 note
⚠️ Walltime results may be unreliableSome benchmarks used the Walltime instrument outside CodSpeed Macro Runners, which can make the results inconsistent.
⚠️ Unable to measure the execution of 2 benchmarksThese benchmarks measured no execution time, so their results are not comparable and count as unchanged. This usually happens when the compiler removes the code under test.
⚠️ 21 benchmarks are dominated by system callsSystem calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.
ℹ️ 40 benchmarks have no flamegraph
The flamegraph wasn't generated: the symbols of the profiling trace could not be resolved, because no information about the language frames was collected.
⚡ 1 improved benchmark
❌ 1 regressed benchmark
✅ 2406 untouched benchmarks
⏩ 12 skipped benchmarks1
Warning
Please fix the performance issues or acknowledge them on CodSpeed.
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | Walltime | bitpack_blocked_compress_avx2 |
6.7 µs | 7.6 µs | -11.43% |
| ⚡ | Walltime | mul_u64_nonnull_neon |
39.6 µs | 20.5 µs | +92.88% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing ct/row-fn-cleanup/canonical-validity (41b6e8b) with develop (dcb4f50)
Footnotes
-
12 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. ↩