ci: install only the uv binary for v4 ingest (drop the workspace sync) - #8517
1 benchmark 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.
⚡ 5 improved benchmarks
❌ 1 regressed benchmark
✅ 1639 untouched benchmarks
⏩ 4 skipped benchmarks1
Warning
Please fix the performance issues or acknowledge them on CodSpeed.
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | Simulation | rebuild_naive |
91.2 µs | 105.4 µs | -13.42% |
| ⚡ | Simulation | encode_varbin[(1000, 4)] |
161.5 µs | 142.2 µs | +13.64% |
| ⚡ | Simulation | encode_varbin[(1000, 2)] |
159.4 µs | 141.7 µs | +12.52% |
| ⚡ | Simulation | bitwise_not_vortex_buffer_mut[128] |
273.6 ns | 244.4 ns | +11.93% |
| ⚡ | Simulation | compact[(4096, 90)] |
867.2 ns | 779.7 ns | +11.22% |
| ⚡ | Simulation | encode_varbin[(1000, 32)] |
164.8 µs | 148.2 µs | +11.22% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing ct/bench-v4-emitter-uv-binary (1485450) with develop (c7c28d8)
Footnotes
-
4 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. ↩