Integrate September Databricks results and consolidate full-path comparisons - #43
Merged
Merged
Conversation
lio-p
approved these changes
Sep 22, 2026
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.
PR #42 added the September Databricks allocation exports. This change integrates those exports into the accepted real-time comparison, publishes the matched evidence and regenerated charts, and documents reproduction across all five systems.
Databricks preparation cost is $695.60475043, including Zerobus ingestion, MV refresh, and estimated Predictive Optimization. Adding $2.64835177 of normalized query cost gives $698.25310220 full-path cost and a 752.4914× cost-runtime product relative to the matched ClickHouse baseline. The accepted query selections remain 189 dashboard observations and 32 drill-down observations, or 820 query jobs per system.
Preparation costs use the supplied active-ingestion allocation window ending at producer completion. Query cost uses the accepted matched observations. Allocated usage, estimated maintenance, and normalized query cost retain their distinct provenance and pricing basis.
The Redshift update applies the documented, benchmark-owner-directed 32-active-RPU writer assumption. The original long-run measurements are retained; the model is explicitly distinguished from original-run billing evidence. SUPER and typed alternatives each reuse the same writer-plus-MSK path once.
Commits separate:
Validation:
No provider rerun is required. Historical stashes and the two unrelated June telemetry screenshots remain local and outside this PR.