You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Update intent-gizmosql to GizmoSQL v1.38.0-intent.8 and DuckDB v1.5.5-intent.8 - #2422
Updates intent-gizmosql to new releases of its two forks: GizmoSQL v1.38.0 and its embedded DuckDB v1.5.5.
Source and release
https://github.com/bddppqs/intent-gizmosql, tag v1.38.0-intent.8: the release this entry installs (portable Linux amd64 and arm64 builds); changes in its CHANGELOG.md and CLICKBENCH-FORK.md.
Both repositories keep their upstream licenses (Apache-2.0 / MIT).
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
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
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
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
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
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
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.
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates
intent-gizmosqlto new releases of its two forks: GizmoSQL v1.38.0 and its embedded DuckDB v1.5.5.Source and release
v1.38.0-intent.8: the release this entry installs (portable Linux amd64 and arm64 builds); changes in itsCHANGELOG.mdandCLICKBENCH-FORK.md.v1.5.5-intent.8; changes in itsCLICKBENCH-FORK.md.Relation to the
gizmosqlentrygizmosqlentry's exceptinstall,query,check,util.shandload(the README says how); the schema (create.sql) and the load SQL are upstream's.Disclosure and labels
tuned: yeslabel, for the reasons the README states. If you prefer a different name or tag, please relabel it.checkrunsSELECT 1;loadpolls 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 withthreadsset to the number of CPUs andzstd_bulk_write_compression_level = 13. The README states each.Reproduction
benchmark.shunattended on fresh instances (Ubuntu 24.04), with no manual steps; could you run it withmachine:all?