chore: test CUDA Arrow Device capsule exports#8624
Conversation
93c8619 to
8ebaae5
Compare
Merging this PR will not alter performance
|
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | Simulation | chunked_varbinview_into_canonical[(1000, 10)] |
168.9 µs | 205.6 µs | -17.83% |
| ⚡ | Simulation | chunked_varbinview_canonical_into[(100, 100)] |
259.5 µs | 224.4 µs | +15.62% |
| ⚡ | Simulation | chunked_varbinview_into_canonical[(100, 100)] |
306.5 µs | 271.3 µs | +12.97% |
| ⚡ | Simulation | bitwise_not_vortex_buffer_mut[128] |
273.6 ns | 244.4 ns | +11.93% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing ad/pycudf4 (b7a5b32) with develop (4a90e13)
Footnotes
-
4 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. ↩
bf5654e to
71f8a1d
Compare
Add vortex_cuda.to_cudf and install optional Vortex Array helpers for cuDF conversion and Arrow C Device export. Keep the conversion path CUDA-only by rejecting unsupported fallback policies and routing cuDF ingestion through fresh Arrow C Device capsules. Expand CUDA Python tests for the convenience API, installed Array methods, Arrow Device export smoke coverage, and capsule ownership paths. Signed-off-by: Alexander Droste <alexander.droste@protonmail.com>
No description provided.