ClickBench is ClickHouse's web-analytics
benchmark: 43 queries over a single wide hits table (~100M rows of real-ish traffic
data). It is heavy on aggregations, GROUP BYs over high-cardinality columns, and
selective string filters, and is the main "wide table scan" workload in CI.
The queries live in clickbench_queries.sql (one query per
line, numbered from Q0 in file order). The harness lives in
src/clickbench.
CI runs this suite from local NVMe as the Clickbench on NVME PR comment, comparing
DataFusion and DuckDB over Parquet, Vortex, and vortex-compact files (plus a native
DuckDB baseline).
Clickbench Sorted on NVME runs the same table sorted by event time, split into 100
shards whose filenames are shuffled so engines cannot rely on file order, exercising sort
pushdown and zone-map-style pruning on a subset of the queries. See
ClickBenchSortedBenchmark.
vx-bench run clickbench --engine datafusion,duckdb --format parquet,vortex
vx-bench run clickbench-sorted --engine datafusion,duckdb --format parquet,vortex--opt files=N runs the partitioned dataset's first N files (of 100, about 1M rows each)
from its own data directory. The known per-query row counts are checked only at 100 files.