Prune plan scans with zoned statistics - #9244
Draft
joseph-isaacs wants to merge 1 commit into
Draft
CodSpeed HQ / CodSpeed Performance Analysis
succeeded
Aug 11, 2026 in 0s
Performance Gate Passed
⚠️ Different runtime environments detected
Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.
⚡ 2 improved benchmarks
✅ 1960 untouched benchmarks
⏩ 89 skipped benchmarks1
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ⚡ | Simulation | cold_misaligned[(64, 256)] |
5.3 ms | 4.4 ms | +21.03% |
| ⚡ | Simulation | compress_fsst[(1000, 64, 4)] |
1,006.1 µs | 907.9 µs | +10.81% |
Tip
Curious why this is faster? Comment @codspeedbot explain why this is faster on this PR, or directly use the CodSpeed MCP with your agent.
Comparing vortex-plan-zoned-pruning (61f20f3) with vortex-plan-scan-v2 (06c1264)
Footnotes
-
89 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. ↩
Loading