Skip to content

DuckDB (Vortex): build Vortex 0.90.0 on DuckDB 2.0 and update results - #3057

Merged
alexey-milovidov merged 1 commit into
ClickHouse:mainfrom
vortex-data:ji/duckdb-vortex-0.90
Nov 15, 2026
Merged

alexey-milovidov merged 1 commit into
ClickHouse:mainfrom
vortex-data:ji/duckdb-vortex-0.90

Conversation

@joseph-isaacs

@joseph-isaacs joseph-isaacs commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor
  • Build duckdb-vortex from source for both duckdb-vortex and duckdb-vortex-partitioned, pinned to vortex-data/duckdb-vortex@59b149b (Vortex 0.90.0 on DuckDB v2.0.0). DuckDB's own INSTALL vortex ships an older Vortex, and the partitioned variant was still on v0.44.0.
  • Building against DuckDB 2.0 needs three fixes: link vortex into the shell explicitly (STATICALLY_LINK_EXTENSIONS), skip C++20 module scanning, which needs clang-scan-deps (CMAKE_CXX_SCAN_FOR_MODULES=OFF), and raise the open-file limit for many-core hosts. install now checks for vortex_version() rather than for the binary, since the plain shell is linked before the extension is built.
  • Add results for both variants on c8g.metal-48xl, c7a.metal-48xl and c8g.4xlarge.

@github-actions

github-actions Bot commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

Results for duckdb-vortex-partitioned are ready for: c6a.metal, c7a.metal-48xl, c8g.metal-48xl.
This pull request is from a fork, so the automation cannot push to it; save this result as duckdb-vortex-partitioned/results/20261105/c8g.metal-48xl.json.
This pull request is from a fork, so the automation cannot push to it; save this result as duckdb-vortex-partitioned/results/20261105/c7a.metal-48xl.json.
This pull request is from a fork, so the automation cannot push to it; save this result as duckdb-vortex-partitioned/results/20261105/c6a.metal.json.
Preview of the benchmark page with these results

Logs:

@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

Results for duckdb-vortex are ready for: c6a.4xlarge, c6a.metal, c7a.metal-48xl, c8g.4xlarge, c8g.metal-48xl.
Results for duckdb-vortex-partitioned are ready for: c6a.2xlarge, c6a.4xlarge, c8g.4xlarge.
This pull request is from a fork, so the automation cannot push to it; save this result as duckdb-vortex/results/20261105/c8g.metal-48xl.json.
This pull request is from a fork, so the automation cannot push to it; save this result as duckdb-vortex/results/20261105/c7a.metal-48xl.json.
This pull request is from a fork, so the automation cannot push to it; save this result as duckdb-vortex-partitioned/results/20261105/c8g.4xlarge.json.
This pull request is from a fork, so the automation cannot push to it; save this result as duckdb-vortex/results/20261105/c6a.metal.json.
This pull request is from a fork, so the automation cannot push to it; save this result as duckdb-vortex-partitioned/results/20261105/c6a.2xlarge.json.
This pull request is from a fork, so the automation cannot push to it; save this result as duckdb-vortex/results/20261105/c8g.4xlarge.json.
This pull request is from a fork, so the automation cannot push to it; save this result as duckdb-vortex-partitioned/results/20261105/c6a.4xlarge.json.
This pull request is from a fork, so the automation cannot push to it; save this result as duckdb-vortex/results/20261105/c6a.4xlarge.json.
Preview of the benchmark page with these results · Comparison with the previous results
The run of duckdb-vortex on c6a.2xlarge did not produce results.

Logs:

@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

Results for duckdb-vortex-partitioned are ready for: c6a.xlarge.
This pull request is from a fork, so the automation cannot push to it; save this result as duckdb-vortex-partitioned/results/20261105/c6a.xlarge.json.
Preview of the benchmark page with these results
The run of duckdb-vortex on c6a.xlarge did not produce results.

Logs:

@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

Results for duckdb-vortex-partitioned are ready for: c6a.large.
This pull request is from a fork, so the automation cannot push to it; save this result as duckdb-vortex-partitioned/results/20261105/c6a.large.json.
Preview of the benchmark page with these results
The run of duckdb-vortex on c6a.large did not produce results.

Logs:

@github-actions

github-actions Bot commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

The run of duckdb-vortex on t3a.small did not produce results.
The run of duckdb-vortex-partitioned on t3a.small did not produce results.

Logs:

Preview of the benchmark page with these results

Build duckdb-vortex from source for both the single-file and the
partitioned variant, pinned to a commit with Vortex 0.90.0 on DuckDB
v2.0.0, and add results for c8g.metal-48xl, c7a.metal-48xl and
c8g.4xlarge. DuckDB's own `INSTALL vortex` ships an older Vortex, and the
partitioned variant was still on v0.44.0.

Building against DuckDB 2.0 needs three fixes: link vortex into the shell
explicitly (STATICALLY_LINK_EXTENSIONS), skip C++20 module scanning, which
needs clang-scan-deps, and raise the open-file limit for many-core hosts.
The install script now checks for vortex_version() rather than for the
binary, since the plain shell is linked before the extension is built.

Rebased onto main after the DuckDB 2.0 bump (ClickHouse#3186): pass -no-agent to
the custom binary in load and query for both variants, so the CLI keeps
its plain output when run from an AI coding agent.

Signed-off-by: Joe Isaacs <joe.isaacs@live.co.uk>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UeniBANoYjsc8bCuAtmkMC

@neuroalexey neuroalexey left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Status: Needs a fix — the new duckdb-vortex results will not show

The rebase brings in main's duckdb-vortex/results/20261110/ (7f7648d). Those runs use the stock DuckDB 2.0 with INSTALL vortex. The website shows only the latest dated copy of each <system>/<machine> pair (README § How To Add a New Result). So duckdb-vortex/results/20261102/c8g.4xlarge.json:3 and the other two 20261102 files stay hidden. After the merge, the site shows numbers that these scripts do not produce.

Please run duckdb-vortex again on this head and add results dated after 20261110. duckdb-vortex-partitioned is fine, because main has nothing newer than 20250806.

At a1264e9, the automated duckdb-vortex runs on c6a.2xlarge and c6a.xlarge gave no results. But duckdb-vortex-partitioned worked on both, with the same install. Is it expected?

I ran main's validator on this head: no errors.

Automated review by neuroalexey

@alexey-milovidov
alexey-milovidov merged commit 017dc6b into ClickHouse:main Nov 15, 2026
2 of 3 checks passed
alexey-milovidov added a commit that referenced this pull request Nov 15, 2026
Vortex 0.90.0 for DataFusion and DuckDB with automated results (replaces #3056, #3057)
@alexey-milovidov

Copy link
Copy Markdown
Member

Thank you! Merged via #3355, together with the other Vortex 0.90.0 PR. The automation cannot push to branches of organization-owned forks, so #3355 adds the results of the automated benchmark runs from this pull request and removes the manually submitted ones.

Techpriester pushed a commit to Techpriester/ClickBench that referenced this pull request Nov 16, 2026
The automated benchmark runs of ClickHouse#3057
produced results for `duckdb-vortex` (5 machines) and `duckdb-vortex-partitioned`
(8 machines). They could not be committed to the PR because it comes from an
organization-owned fork, so they are added here, and the manually added result
files are removed, as the collector does for PRs it can push to.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch is waiting to be deployed

1 waiting deployment
benchmark-approval — e4bd1118 Waiting Nov 12, 2026 by joseph-isaacs via launch #1162
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

machine:all PR benchmark on every machine type

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants