# Cluster sizes
Reference for Materialize Cloud cluster sizes and their resource allocations.
Materialize Cloud clusters come in two families of sizes: `cc` sizes and `M.1`
sizes. We recommend `cc` sizes for most workloads; `M.1` sizes provide access
to additional disk capacity, which can be beneficial for disk-intensive
workloads. See [`CREATE CLUSTER`](/sql/create-cluster/) for details on
choosing between them.

## cc cluster sizes

> **Note:** The values set forth in the table are solely for illustrative purposes.
> Materialize reserves the right to change the capacity at any time. As such, you
> acknowledge and agree that those values in this table may change at any time,
> and you should not rely on these values for any capacity planning.

For Materialize Cloud, `cc` cluster sizes have the following default resource
allocations:

| Size | CPU Limit | Memory Limit | Disk Limit | Credits/Hour |
| --- | --- | --- | --- | --- |
| `25cc` | `0.5` | `3881MiB` | `7762MiB` | `0.25` |
| `50cc` | `1` | `7762MiB` | `15525MiB` | `0.5` |
| `100cc` | `2` | `15525MiB` | `31050MiB` | `1` |
| `200cc` | `4` | `31050MiB` | `62100MiB` | `2` |
| `300cc` | `6` | `46575MiB` | `93150MiB` | `3` |
| `400cc` | `8` | `62100MiB` | `124201MiB` | `4` |
| `600cc` | `12` | `93150MiB` | `186301MiB` | `6` |
| `800cc` | `16` | `124201MiB` | `248402MiB` | `8` |
| `1200cc` | `24` | `186301MiB` | `372603MiB` | `12` |
| `1600cc` | `31` | `240640MiB` | `481280MiB` | `16` |
| `3200cc` | `62` | `481280MiB` | `962560MiB` | `32` |
| `6400cc` | `62` | `481280MiB` | `962560MiB` | `64` |


To confirm the current resource allocations for a size, query the
[`mz_cluster_replica_sizes`](/sql/system-catalog/mz_catalog/#mz_cluster_replica_sizes)
system catalog table.

## M.1 cluster sizes

> **Note:** The values set forth in the table are solely for illustrative purposes.
> Materialize reserves the right to change the capacity at any time. As such, you
> acknowledge and agree that those values in this table may change at any time,
> and you should not rely on these values for any capacity planning.

`M.1` sizes report a single **Total Capacity** value instead of separate
memory and disk figures: the value is the combined memory-and-disk pool
available to the cluster, not two independent limits. For example, an
`M.1-xsmall` cluster has 106 GiB of combined capacity to split between memory
and disk, not 106 GiB of each.


| Cluster size | Compute Credits/Hour | Total Capacity | Notes |
| --- | --- | --- | --- |
| <strong>M.1-nano</strong> | 0.75 | 26 GiB |  |
| <strong>M.1-micro</strong> | 1.5 | 53 GiB |  |
| <strong>M.1-xsmall</strong> | 3 | 106 GiB |  |
| <strong>M.1-small</strong> | 6 | 212 GiB |  |
| <strong>M.1-medium</strong> | 9 | 318 GiB |  |
| <strong>M.1-large</strong> | 12 | 424 GiB |  |
| <strong>M.1-1.5xlarge</strong> | 18 | 636 GiB |  |
| <strong>M.1-2xlarge</strong> | 24 | 849 GiB |  |
| <strong>M.1-3xlarge</strong> | 36 | 1273 GiB |  |
| <strong>M.1-4xlarge</strong> | 48 | 1645 GiB |  |
| <strong>M.1-8xlarge</strong> | 96 | 3290 GiB |  |
| <strong>M.1-16xlarge</strong> | 192 | 6580 GiB | Available upon request |
| <strong>M.1-32xlarge</strong> | 384 | 13160 GiB | Available upon request |
| <strong>M.1-64xlarge</strong> | 768 | 26320 GiB | Available upon request |
| <strong>M.1-128xlarge</strong> | 1536 | 52640 GiB | Available upon request |


See also:

- [Materialize service consumption
  table](https://materialize.com/pdfs/pricing.pdf).

- [Blog: Scaling Beyond Memory: How Materialize Uses Swap for Larger
  Workloads](https://materialize.com/blog/scaling-beyond-memory/).