Repository navigation
perf(layout): lower zoned pruning predicates once - #10428
Performance Regression: -35.31%
⚠️ 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.
⚠️ 1 benchmark measured no execution time
Nothing ran under measurement, usually because the compiler removed the code under test. This result is not comparable, so it counts as unchanged.
⚠️ 12 benchmarks spent significant time in system calls
System calls cannot be consistently instrumented, so they are not included in the measure, which understates the real cost. Please switch to the Walltime instrument to accurately measure system calls.
❌ 1 regressed benchmark
✅ 2182 untouched benchmarks
⏩ 184 skipped benchmarks1
Warning
Please fix the performance issues or acknowledge them on CodSpeed.
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | Simulation | decode_primitives[i64, (1000, 32)] |
25 µs | 38.6 µs | -35.31% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing rk/zoned-prepare-pruning-predicate (ba16698) with develop (9c7b782)
Footnotes
-
184 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. ↩