refactor: build known scan expressions as bound expressions directly - #9269
refactor: build known scan expressions as bound expressions directly#9269joseph-isaacs wants to merge 1 commit into
Performance Regression: -4.4%
⚡ 1 improved benchmark
❌ 2 regressed benchmarks
✅ 1926 untouched benchmarks
⏩ 51 skipped benchmarks1
Warning
Please fix the performance issues or acknowledge them on CodSpeed.
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | Simulation | chunked_dict_primitive_into_canonical[u32, (1000, 10, 100)] |
1.6 ms | 1.9 ms | -11.41% |
| ❌ | Simulation | chunked_dict_primitive_into_canonical[u32, (1000, 100, 100)] |
1.7 ms | 1.9 ms | -10.44% |
| ⚡ | Simulation | chunked_varbin_opt_to_varbinview_builder[(10, 100)] |
870.4 µs | 790.5 µs | +10.11% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing claude/ji-optimal-bound-exprs (cc7d9f4) with develop (c1ae775)2
Footnotes
-
51 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. ↩
-
No successful run was found on
develop(6a8d248) during the generation of this report, so c1ae775 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩