Skip to content

Update intent-gizmosql to GizmoSQL v1.38.0-intent.8 and DuckDB v1.5.5-intent.8 - #2422

Open
ZENGXH wants to merge 6 commits into
ClickHouse:mainfrom
ZENGXH:intent-gizmosql
Open

ZENGXH wants to merge 6 commits into
ClickHouse:mainfrom
ZENGXH:intent-gizmosql

Conversation

@ZENGXH

@ZENGXH ZENGXH commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

Updates intent-gizmosql to new releases of its two forks: GizmoSQL v1.38.0 and its embedded DuckDB v1.5.5.

Source and release

Relation to the gizmosql entry

  • Every script is the upstream gizmosql entry's except install, query, check, util.sh and load (the README says how); the schema (create.sql) and the load SQL are upstream's.

Disclosure and labels

  • The entry keeps the tuned: yes label, for the reasons the README states. If you prefer a different name or tag, please relabel it.
  • Compared with the merged entry (intent.2): the server's caches also keep stored code translations and their byte lengths, and row-group metadata; check runs SELECT 1; load polls for the server to stop and to start every 50 ms and, on machines with more than 64 CPUs and one thread per core, runs the bulk insert with threads set to the number of CPUs and zstd_bulk_write_compression_level = 13. The README states each.

Reproduction

  • No result file is included; the entry's current results are the previous update's, for your runs to replace. We ran benchmark.sh unattended on fresh instances (Ubuntu 24.04), with no manual steps; could you run it with machine:all?

@ZENGXH ZENGXH changed the title Update intent-gizmosql to GizmoSQL v1.38.0-intent.3 and DuckDB v1.5.5-intent.3 Update intent-gizmosql to GizmoSQL v1.38.0-intent.5 and DuckDB v1.5.5-intent.5 Oct 6, 2026
@ZENGXH

ZENGXH commented Oct 6, 2026

Copy link
Copy Markdown
Contributor Author

We updated this PR to the newer releases of the two forks: the entry now installs GizmoSQL v1.38.0-intent.5 with DuckDB v1.5.5-intent.5 instead of intent.3. No result file is included.

@ZENGXH ZENGXH changed the title Update intent-gizmosql to GizmoSQL v1.38.0-intent.5 and DuckDB v1.5.5-intent.5 Update intent-gizmosql to GizmoSQL v1.38.0-intent.6 and DuckDB v1.5.5-intent.6 Oct 9, 2026
@ZENGXH

ZENGXH commented Oct 9, 2026

Copy link
Copy Markdown
Contributor Author

We updated this PR to the newer releases of the two forks: the entry now installs GizmoSQL v1.38.0-intent.6 with DuckDB v1.5.5-intent.6 instead of intent.5, and load polls for the server to stop and to start every 50 ms. No result file is included.

@ZENGXH ZENGXH changed the title Update intent-gizmosql to GizmoSQL v1.38.0-intent.6 and DuckDB v1.5.5-intent.6 Update intent-gizmosql to GizmoSQL v1.38.0-intent.8 and DuckDB v1.5.5-intent.8 Oct 9, 2026
@ZENGXH

ZENGXH commented Oct 9, 2026

Copy link
Copy Markdown
Contributor Author

We updated this PR to the newer releases of the two forks: the entry now installs GizmoSQL v1.38.0-intent.8 with DuckDB v1.5.5-intent.8 instead of intent.6, and, on machines with more than 64 CPUs and one thread per core, load runs the bulk insert with threads set to the number of CPUs and zstd_bulk_write_compression_level = 13. No result file is included.

@ZENGXH
ZENGXH requested a deployment to benchmark-approval October 9, 2026 20:14 — with GitHub Actions Waiting
@ZENGXH

ZENGXH commented Oct 9, 2026

Copy link
Copy Markdown
Contributor Author

Hi @alexey-milovidov, when you have time, could you take a look at this PR and start the benchmark run for it? It updates the intent-gizmosql entry to the intent.8 releases of the two forks, with no result file included. The entry installs pinned amd64 and arm64 release zips verified by SHA-256, and before updating we ran it end to end on each of the nine benchmark machines. If anything should change, we're happy to adjust it. Thank you!

This branch is waiting to be deployed

1 waiting deployment
benchmark-approval — 2369853a Waiting Oct 9, 2026 by ZENGXH via launch #724
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant