Skip to content

Late materialization for duckdb#7720

Closed
myrrc wants to merge 1 commit intodevelopfrom
myrrc/duckdb-late-materialization
Closed

Late materialization for duckdb#7720
myrrc wants to merge 1 commit intodevelopfrom
myrrc/duckdb-late-materialization

Conversation

@myrrc
Copy link
Copy Markdown
Contributor

@myrrc myrrc commented Apr 29, 2026

Add file_index, file_row_number virtual columns.
Add file-based filtering (range, selection) to ScanRequest.
Add partition index method.
Add late materialization support and row id columns support in duckdb.

@myrrc myrrc requested a review from joseph-isaacs April 29, 2026 15:05
@myrrc myrrc added changelog/performance A performance improvement ext/duckdb Relates to the DuckDB integration labels Apr 29, 2026
Signed-off-by: Mikhail Kot <to@myrrc.dev>
@myrrc myrrc force-pushed the myrrc/duckdb-late-materialization branch from 243de42 to 8a0b20b Compare April 29, 2026 15:05
@myrrc myrrc closed this Apr 29, 2026
@codspeed-hq
Copy link
Copy Markdown

codspeed-hq Bot commented Apr 29, 2026

Merging this PR will degrade performance by 43.85%

⚠️ 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.

⚡ 2 improved benchmarks
❌ 3 regressed benchmarks
✅ 1193 untouched benchmarks
⏩ 33 skipped benchmarks1

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Mode Benchmark BASE HEAD Efficiency
WallTime for[10M_u8] 73.8 µs 131.5 µs -43.85%
WallTime mix[0%_in/100%_out] 277.5 µs 226.3 µs +22.62%
WallTime for[10M_u16] 96.2 µs 160 µs -39.89%
WallTime for[10M_u32] 165.8 µs 115.3 µs +43.8%
Simulation bitwise_not_vortex_buffer_mut[128] 246.1 ns 275.3 ns -10.6%

Comparing myrrc/duckdb-late-materialization (8a0b20b) with develop (e3a6b62)

Open in CodSpeed

Footnotes

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog/performance A performance improvement ext/duckdb Relates to the DuckDB integration

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant