Lock file maintenance - #9563
Performance Regression: -3.27%
⚠️ 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.
⚡ 3 improved benchmarks
❌ 2 regressed benchmarks
✅ 2176 untouched benchmarks
⏩ 206 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.8 µs | 20.3 µs | -37.27% |
| ❌ | Simulation | random_i8[0.5] |
67.2 µs | 90.7 µs | -25.92% |
| ⚡ | Simulation | random_i16[0.8] |
92.1 µs | 74.1 µs | +24.35% |
| ⚡ | Simulation | decompress[u64, (4000, 1024)] |
85.7 µs | 70.5 µs | +21.53% |
| ⚡ | WallTime | arrow_checked_add_u32_avx512[16384] |
21.2 µs | 17.6 µs | +20.55% |
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-js-lock-file-maintenance (f81ce13) with develop (dab1684)
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. ↩