Experiment: compose scheme registration with output editions - #10040
connortsui20 wants to merge 3 commits into
2 benchmarks 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.
⚠️ 3 benchmarks measured no execution time
Nothing ran under measurement, usually because the compiler removed the code under test. These results are not comparable, so they count as unchanged.
⚠️ Different runtime environments detected
Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.
⚡ 2 improved benchmarks
❌ 2 regressed benchmarks
✅ 2218 untouched benchmarks
⏩ 343 skipped benchmarks1
🗄️ 1 archived benchmark run2
Warning
Please fix the performance issues or acknowledge them on CodSpeed.
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | WallTime | decode_avx512[8192, (Inline, OneNullInEight)] |
81.7 µs | 99.2 µs | -17.65% |
| ❌ | WallTime | decode_avx512[8192, (Inline, AllValid)] |
96.6 µs | 112.5 µs | -14.12% |
| ⚡ | Simulation | from_vec_drop_arrow[16384] |
40.4 µs | 31.4 µs | +28.7% |
| ⚡ | WallTime | filtered_sink_i64_avx512[OneNullInEight] |
26.3 µs | 22.3 µs | +18.26% |
| Simulation | fixed_16_advancing_ptr_safe[100] |
< 1 ns | < 1 ns | N/A | |
| Simulation | preverify_advancing_ptr_unchecked[1000] |
< 1 ns | < 1 ns | N/A | |
| Simulation | preverify_advancing_ptr_unchecked[10000] |
< 1 ns | < 1 ns | N/A |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing ct/composable-schemes (ffe45b2) with develop (035aeff)
Footnotes
-
343 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. ↩
-
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. ↩