Skip to content

feat(cuda): support column projection and dictionary decoding in file scans - #9934

Merged
0ax1 merged 35 commits into
developfrom
ad/cuda-projected-file-scans
Sep 22, 2026
Merged

0ax1 merged 35 commits into
developfrom
ad/cuda-projected-file-scans

fix(ffi): regenerate header after error safety docs

39ddfa5
Select commit
Loading
Failed to load commit list.
CodSpeed / CodSpeed Performance Analysis failed Sep 22, 2026 in 0s

1 benchmark regressed

⚠️ 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.

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

⚡ 3 improved benchmarks
❌ 1 regressed benchmark
✅ 2246 untouched benchmarks
⏩ 251 skipped benchmarks1
🗄️ 1 archived benchmark run2

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Mode Benchmark BASE HEAD Efficiency
Simulation take_fsl_u32_random[256, 10] 124.4 µs 162.3 µs -23.33%
Simulation take_fsl_u32_random[16, 100] 165.8 µs 126 µs +31.64%
Simulation take_fsl_nullable_random[16, 100] 187.6 µs 165.4 µs +13.41%
Simulation take_fsl_f16_random[256, 100] 231.8 µs 204.8 µs +13.18%

Tip

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


Comparing ad/cuda-projected-file-scans (39ddfa5) with develop (5c1671e)

Open in CodSpeed

Footnotes

  1. 251 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.

  2. 1 benchmark was run, but is now archived. If it was deleted in another branch, consider rebasing to remove it from the report. Instead if it was added back, click here to restore it.