Skip to content

duckdb: propagate per-file "partition" stats - #9639

Open
myrrc wants to merge 3 commits into
developfrom
myrrc/duckdb-partition-stats
Open

duckdb: propagate per-file "partition" stats#9639
myrrc wants to merge 3 commits into
developfrom
myrrc/duckdb-partition-stats

split tests

8b3244b
Select commit
Loading
Failed to load commit list.
CodSpeed HQ / CodSpeed Performance Analysis failed Aug 26, 2026 in 0s

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.

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

⚡ 5 improved benchmarks
❌ 1 regressed benchmark
✅ 2106 untouched benchmarks
⏩ 106 skipped benchmarks1
🗄️ 4 archived benchmarks run2

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Mode Benchmark BASE HEAD Efficiency
WallTime arrow_checked_add_u32_avx2[16384] 17.7 µs 21.3 µs -16.81%
WallTime arrow_checked_add_u32_neon[16384] 20.4 µs 13.5 µs +50.76%
WallTime arrow_checked_add_u32_avx512[16384] 21.3 µs 17.6 µs +20.72%
Simulation take[duplicates/repeated/primitive/nonnull/chunks=16/indices=1000] 245 µs 207 µs +18.39%
WallTime words_gather_dispatch_avx512[1024] 9 ns 8 ns +12.5%
WallTime mul_u32_nonnull_avx512 6.3 µs 5.7 µs +10.4%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.


Comparing myrrc/duckdb-partition-stats (8b3244b) with develop (ee1ac25)

Open in CodSpeed

Footnotes

  1. 106 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.

  2. 4 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.