Move protobuf and flatbuffer definitions into their owning crates - #9550
3 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.
⚠️ Different runtime environments detected
Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.
⚡ 6 improved benchmarks
❌ 3 regressed benchmarks
✅ 2230 untouched benchmarks
⏩ 176 skipped benchmarks1
🗄️ 1 archived benchmark run2
Warning
Please fix the performance issues or acknowledge them on CodSpeed.
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | Simulation | decompress[u64, (4000, 1024)] |
71.8 µs | 86 µs | -16.47% |
| ❌ | WallTime | filtered_owned_i64_avx512[OneNullInEight] |
22.3 µs | 26.1 µs | -14.51% |
| ❌ | WallTime | mul_u32_nonnull_avx512 |
5.6 µs | 6.3 µs | -11.54% |
| ⚡ | WallTime | dict_canonicalize_gt_u8_avx2[16000000] |
11.1 ms | 7.1 ms | +57.38% |
| ⚡ | WallTime | mul_u64_nonnull_neon |
20.7 µs | 15.5 µs | +33.5% |
| ⚡ | WallTime | filtered_owned_i64_avx2[OneNullInEight] |
26 µs | 22.4 µs | +15.68% |
| ⚡ | WallTime | multiply_shapes_neon[(16384, PerRowPerRow)] |
20.2 µs | 17.5 µs | +15.57% |
| ⚡ | WallTime | mul_i64_nonnull_neon |
20.1 µs | 17.5 µs | +14.78% |
| ⚡ | WallTime | words_gather_scalar_avx2[65536] |
9.4 µs | 8.2 µs | +13.79% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing claude/protobuf-codegen-build-rs-s897y8 (f1ebf01) with develop (f9093df)
Footnotes
-
176 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. ↩