docs: add Materialize Cloud cluster sizes reference - #38792
Open
maheshwarip wants to merge 1 commit into
Open
Conversation
Replaces the cc-to-M.1 size mapping guide with a "Cluster sizes" page under Materialize Cloud docs that lists exact resource allocations (CPU, memory, disk, credits/hour) for cc sizes, and clarifies that the M.1 "Total Capacity" figure is a combined memory-and-disk pool rather than two separate limits. Closes: EDU-73 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014CeaDCfsZEupnH8Hs34ems
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
2 participants
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.
Motivation
Closes EDU-73. A customer asked where to find memory/disk limits for Cloud clusters (internal Slack thread); the old
cc to M.1 size mappingpage only mapped sizes to each other, not to actual resource numbers.Description
/materialize-cloud/cluster-sizes/, with two sections:materialize-cloud/cluster-sizes-ccshortcode (HTML + skill.md variants) that reads the existingself_managed_cluster_sizes.ymldata (same underlying allocations, already used for the self-managed appendix page — single-sourced, no new numbers introduced).m1_cluster_sizing.ymltable (already shipped onsql/create-cluster), with added prose clarifying that "Total Capacity" is a combined memory+disk pool, not two separate limits.clusters/m1-cc-mapping.mdand its two now-unused mapping data files, and repoints the three "See also" links from the SQL reference pages to the new page. Old URLs 301 viaaliases.ccsize resource numbers (the source-of-truth lives in thecloudrepo, out of scope here); I'm reusing the self-managed default allocations, which line up with Cloud's published credits/hour progression. Worth a sanity check from someone with Cloud pricing/infra context before merge.Verification
Built both output targets locally (
hugoHTML +hugo --config config.toml,config.skill.tomlmarkdown) and ranhtmltest: no new broken links or render issues from this change (pre-existing failure on an unrelatedcreate-sink/kafkaanchor).🤖 Generated with Claude Code
https://claude.ai/code/session_014CeaDCfsZEupnH8Hs34ems