Skip to content

test(clickhouse): measure automatically selected SUM and MAX plans - #629

Merged
zzylol merged 3 commits into
mainfrom
eval/clickhouse-automatic-benefits
Sep 11, 2026
Merged

zzylol merged 3 commits into
mainfrom
eval/clickhouse-automatic-benefits

Conversation

@zzylol

@zzylol zzylol commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

The previous ClickHouse benefit probe supplied a MinMax catalog, so it did not demonstrate automatic materialization selection. This change sends only SQL/schema/accuracy/time bounds through the real Planner and control-plane catalog builder, records the selected DAG and candidate trace, and exercises the installed state through a separate backend process.

Before: the bounded MAX measurement used a predeclared winning family. After: both SUM and MAX probes use automatically selected materializations, and a stdin example exposes the same publication/trace for independent inspection. Six controlled trials cover 6,000 warm and 6,000 exact requests with identical numeric results. Median repeated-query speedup is 5.51–8.01x for SUM and 7.87–8.88x for MAX; the report includes CPU, backfill, first-query, RSS and storage observations plus raw-trace hashes and runtime budgets.

These are bounded single-series aggregate sensitivity results, not original 27-query workload coverage. The deployment retains ClickHouse, so combined memory/storage are not lower. Construction costs, mismatched retained durations, unavailable estimated costs and a failed quantile frontend probe are stated explicitly.

Verification: release builds, a real automatic SUM process smoke test, six matched two-CPU/4-GiB process trials (1,000 warm plus 1,000 exact requests each), and bash -n for the reproduction runner. Runtime results identify their exact measured source/executable hashes; subsequent main replay does not change those historical measurements. Independent artifact review passed: all raw-trace hashes, request counts, numeric equality, median ratios and process budgets were checked.

@zzylol
zzylol marked this pull request as ready for review September 11, 2026 02:03
@zzylol
zzylol merged commit 63427d4 into main Sep 11, 2026
1 check passed
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