Repository navigation
Compose and drive a V2 scan in DataFusion - #10708
joseph-isaacs wants to merge 6 commits into
1 benchmark regressed
2 warnings, 1 note
⚠️ Walltime results may be unreliableSome benchmarks used the Walltime instrument outside CodSpeed Macro Runners, which can make the results inconsistent.
⚠️ 23 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.3% |
| ⚡ | Walltime | threshold_neon[80] |
4 µs | 3.5 µs | +13.48% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing ji/scan-v2-chain-3-drivers (25458e3) with ji/scan-v2-chain-2-planners (26c4265)2
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. ↩
-
No successful run was found on
ji/scan-v2-chain-2-planners(c441bc4) during the generation of this report, so 872b4d1 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩