Repository navigation
duckdb: keep pushed filters visible to the join planner - #10941
robert3005 wants to merge 1 commit into
Performance Regression: -10.67%
2 warnings
⚠️ Walltime results may be unreliableSome benchmarks used the Walltime instrument outside CodSpeed Macro Runners, which can make the results inconsistent.
⚠️ 1 benchmark is dominated by system callsSystem calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.
❌ 1 regressed benchmark
✅ 2269 untouched benchmarks
⏩ 370 skipped benchmarks1
🗄️ 30 archived benchmarks run2
Warning
Please fix the performance issues or acknowledge them on CodSpeed.
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | Walltime | threshold_neon[64] |
3.9 µs | 4.4 µs | -10.67% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing rk/duckdb-scan-estimates (6c0f397) with develop (3953e98)
Footnotes
-
370 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. ↩
-
30 benchmarks were run, but are now archived. If they were deleted in another branch, consider rebasing to remove them from the report. Instead if they were added back, click here to restore them. ↩