duckdb: return projection_ids handling - #9887
Performance Regression: -16.97%
⚠️ 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.
⚡ 1 improved benchmark
❌ 5 regressed benchmarks
✅ 2196 untouched benchmarks
⏩ 218 skipped benchmarks1
Warning
Please fix the performance issues or acknowledge them on CodSpeed.
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | WallTime | arrow_checked_add_u32_neon[16384] |
12.3 µs | 20.4 µs | -39.77% |
| ❌ | Simulation | random_i8[0.5] |
70.6 µs | 94.5 µs | -25.31% |
| ❌ | Simulation | decompress[u64, (4000, 1024)] |
72 µs | 87.5 µs | -17.74% |
| ❌ | WallTime | words_gather_scalar_avx2[65536] |
8.3 µs | 9.4 µs | -11.95% |
| ❌ | WallTime | mul_i32_nonnull_avx512 |
7.2 µs | 8 µs | -10.01% |
| ⚡ | Simulation | allocate_drop_arrow[0] |
516.4 ns | 462.3 ns | +11.72% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing myrrc/duckdb-projection-ids (c2a946f) with develop (313bc4f)
Footnotes
-
218 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. ↩