Repository navigation
[EXPERIMENTAL] perf: make checked lane chunking opt-in - #10304
connortsui20 wants to merge 3 commits into
Performance Gate Passed
⚠️ 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.
⚠️ 2 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.
⚡ 5 improved benchmarks
✅ 2090 untouched benchmarks
⏩ 518 skipped benchmarks1
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ⚡ | WallTime | mul_i32_nonnull_avx2 |
32.7 µs | 18.4 µs | +78.1% |
| ⚡ | WallTime | mul_i32_nullable_avx2 |
33.9 µs | 19.5 µs | +73.65% |
| ⚡ | WallTime | mul_i16_nonnull_avx2 |
29.1 µs | 21.7 µs | +34.06% |
| ⚡ | WallTime | mul_i16_nonnull_avx512 |
16.5 µs | 14.7 µs | +12.55% |
| ⚡ | WallTime | mul_i16_nonnull_neon |
24 µs | 21.6 µs | +10.99% |
| Simulation | density_sweep_dense_runs[0.9] |
55.7 µs | < 1 ns | N/A | |
| Simulation | bench_compare_sliced_dict_primitive[(3333, 10000)] |
79.7 µs | < 1 ns | N/A |
Tip
Curious why performance improved? Comment @codspeedbot explain why performance improved on this PR, or directly use the CodSpeed MCP with your agent.
Comparing ct/checked-lane-chunks-opt-in (b6ff4dc) with develop (76381d5)
Footnotes
-
518 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. ↩