[0ax1]

Problem

Vortex's CUDA consumers still use cudarc and cannot use the new driver's access tracking.

Solution

Migrate consumers to vortex-cuda-driver, move i256 support into its optional feature, and remove cudarc.

Assessment

Changes public CUDA types and removes vortex-array's cudarc feature. The driver stays unpublished. Builds on the merged CUDA PRs.

[codspeed]

Merging this PR will regress 4 benchmarks

4 warnings, 1 note

⚠️ Walltime results may be unreliable

Some benchmarks used the Walltime instrument outside CodSpeed Macro Runners, which can make the results inconsistent.

Learn more about Macro Runners

See affected benchmarks

⚠️ Unable to measure the execution of 1 benchmark

This benchmark measured no execution time, so its result is not comparable and counts as unchanged. This usually happens when the compiler removes the code under test.

Prevent compiler optimizations

See affected benchmarks

⚠️ 17 benchmarks are dominated by system calls

System 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.

Learn more about system calls

See affected benchmarks

⚠️ Base and head ran on different runner types

Some benchmarks with significant performance changes were compared across different runner types, so the changes might not come from the code. Run base and head on the same runner type, or use CodSpeed Macro Runners for more stable results.

Learn more about Macro Runners

Open the report in CodSpeed to investigate

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

See affected benchmarks

⚡ 7 improved benchmarks
❌ 4 regressed benchmarks
✅ 2397 untouched benchmarks
⏩ 12 skipped benchmarks¹
🗄️ 43 archived benchmarks run²

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	CPU Simulation	test_scan_filter_to_arrow_array[int_float]	3.5 ms	4.1 ms	-13.67%
❌	CPU Simulation	test_repeated_scan_filter[int_float]	3.4 ms	3.9 ms	-10.9%
❌	CPU Simulation	test_repeated_scan_filter[int]	2.4 ms	2.7 ms	-10.32%
❌	CPU Simulation	test_scan_filter_to_arrow_array[int]	2.5 ms	2.8 ms	-10.16%
⚡	Walltime	filter_neon[8]	1,779 ns	886 ns	×2
⚡	Walltime	threshold_neon[80]	5.1 µs	3.3 µs	+53.63%
⚡	Walltime	filter_neon[64]	2.4 µs	1.7 µs	+38.12%
⚡	Walltime	threshold_neon[8]	1.8 µs	1.4 µs	+33.63%
⚡	CPU Simulation	bench_compare_primitive[(10000, 32)]	97 µs	72.9 µs	+33.09%
⚡	Walltime	filter_neon[80]	3.2 µs	2.5 µs	+31.16%
⚡	Walltime	threshold_neon[64]	3.1 µs	2.6 µs	+19.97%

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-driver-migration (e216787) with develop (a74fdc7)}

Footnotes

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

2. 43 benchmarks were run, but are now archived. If they were deleted in another branch, consider rebasing to remove them from the report. Instead if they were added back, click here to restore them. ↩