Repository navigation
Add reader core scaling measurements with hot and cold caches - #46
Merged
Merged
Conversation
lio-p
approved these changes
Oct 13, 2026
tom-clickhouse
marked this pull request as ready for review
October 13, 2026 11:38
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This adds reproducible reader CPU scaling measurements for Blog 6 11c, using the original D1/D2 drill-down queries against the fixed 113.2B-quote dataset. The current cache-controlled sweep measures 2, 4, 8, 16, 30 and 59 cores on one fixed 59-vCPU / 236-GiB node, with
max_threadscontrolling query parallelism. It does not compare six physically resized services.The selected visual compares Hot caches with Cold data caches and query-condition caching off. Pooled uncompressed throughput rises from 0.803 to 15.560 GB/s for Hot and 0.731 to 9.848 GB/s for Cold. Gains taper at larger settings; the package does not claim perfect linear scaling. A separate condition-cache-on cold treatment and earlier 16/59-vCPU exploratory ledgers remain intact, without being spliced into the selected curves.
The cache pilot demonstrated that filesystem-cache-off alone still read through the userspace page cache. Cold treatments therefore bypass filesystem, page, and distributed data-cache reads per query. Profile counters verify positive S3 reads and zero page/distributed reads for Cold, and page hits with zero S3 reads/misses for Hot. Query-result caching remains disabled. Metadata/mark caches are not globally purged.
Included: exact source/treatment SQL, shuffled trial plans, append-only HTTP records, full query-log CSVs/ProfileEvents/Settings, capacity/version/data/cache checks, derived statistics, reports, offline analysis, live repeat instructions, and SHA-256 manifests.
derive_visual.pyreproduces the exact 11c payload and resource CSV: CPU used/headroom relative to the selected core budget and average measured per-query memory peaks. Throughput per core uses consumed CPU seconds, matching 11a.Validation:
Start at
full-path-realtime/quotes/clickhouse-cloud/experiments/reader-thread-scaling/README.md, then2026-10-11-cache-modes/README.mdfor selected cases and reproduction steps. Original Run 2 continuous-ingestion evidence remains separate in PR #44; this experiment does not recreate its historical cache state or 3.25 GB/s display endpoint.