Lock file maintenance - #9139
Performance Regression: -3.57%
⚠️ 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
❌ 3 regressed benchmarks
✅ 2195 untouched benchmarks
⏩ 206 skipped benchmarks1
Warning
Please fix the performance issues or acknowledge them on CodSpeed.
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | WallTime | mul_u32_nonnull_avx512 |
5.6 µs | 6.3 µs | -10.84% |
| ❌ | Simulation | allocate_drop_vortex_minimal_alignment[0] |
901.5 ns | 1,009.9 ns | -10.73% |
| ❌ | Simulation | allocate_drop_vortex[0] |
957.4 ns | 1,065.8 ns | -10.16% |
| ⚡ | WallTime | arrow_checked_add_u32_avx512[16384] |
21.2 µs | 17.6 µs | +20.95% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing renovate/lock-file-maintenance-rust-lock-file-maintenance (25cac21) with develop (89d2f61)
Footnotes
-
206 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. ↩