> For the complete documentation index, see [llms.txt](https://docs.silk.us/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silk.us/deploy/plan-your-deployment/plan-datapod-capacity.md).

# Plan DataPod Capacity

Learn how Silk measures capacity and what to consider when sizing a DataPod for current and future workloads.

Capacity planning helps ensure that a DataPod can support your current workload, future data growth, and operational activities. Before deploying a DataPod, understand how Silk measures capacity and which capacity decisions can​ — and can’t — be changed later.

A DataPod's [deployment profile](/learn/products-and-core-concepts/datapod-architecture/datapod-deployment-profiles.md) determines the capacity ranges, node configurations, and scaling options available on the DataPod.

{% hint style="warning" %}
**Plan for future growth**

The allocated capacity limit is set when the DataPod is created and can’t be changed afterward. Plan for anticipated growth before selecting this limit.
{% endhint %}

## DataPod capacity overview

The SDP Management Console reports **provisioned**, **allocated** and **physical** capacity. Together, these measurements show how much storage has been configured, how much data has been written, and how much physical space that data consumes.

{% tabs %}
{% tab title="Provisioned Capacity" %}
Provisioned capacity represents that total configured capacity assigned to volumes, clones, views, and snapshots, regardless of how much data has been written.

It reflects the storage made available to application and database workloads and is used for database sizing and Silk licensing. Resources can be treated differently for licensing purposes: full volume clones contribute to licensed provisioned volume capacity, while thin clones do not.
{% endtab %}

{% tab title="Allocated Capacity" %}
Allocated capacity, also called logical capacity, represents the amount of space used before compression and deduplication are applied.
{% endtab %}

{% tab title="Physical Capacity" %}
Physical capacity represents the space consumed after applicable compression and deduplication savings.

Physical capacity is provided by the DataPod's m.nodes.
{% endtab %}
{% endtabs %}

Since Silk uses thin provisioning and data reduction, provisioned capacity can be greater than allocated capacity, and allocated capacity can be greater than physical capacity:

<table data-view="cards"><thead><tr><th align="center"></th><th align="center"></th><th align="center"></th></tr></thead><tbody><tr><td align="center"><h2><i class="fa-ruler-combined" style="color:$primary;">:ruler-combined:</i></h2></td><td align="center"><strong>Provisioned Capacity</strong></td><td align="center">Storage configured and made available to workloads through Silk volumes.</td></tr><tr><td align="center"><h2><i class="fa-chart-pie" style="color:$primary;">:chart-pie:</i></h2></td><td align="center"><strong>Allocated Capacity</strong></td><td align="center">Storage actually consumed before data reduction.</td></tr><tr><td align="center"><h2><i class="fa-hard-drive" style="color:$primary;">:hard-drive:</i></h2></td><td align="center"><strong>Physical Capacity</strong></td><td align="center">Storage consumed on disk after data reduction.</td></tr></tbody></table>

The difference between **provisioned and allocated capacity** reflects the effect of thin provisioning. Capacity can be made available to workloads without being consumed until data is written.

The difference between **allocated and physical capacity** reflects the effects of compression and deduplication.

Actual capacity consumption and data-reduction results depend on workload characteristics and the data services enabled for each volume.

{% hint style="info" %}
Silk reports capacity in tebibytes (TiB). One TiB equals approximately 1.10 terabytes (TB).
{% endhint %}

### What determines capacity

DataPod capacity limits depend on several configuration choices:

* **Deployment profile:** Determines the supported capacity ranges and available c.node and m.node options.
* **c.node configuration:** Affects performance, availability requirements, and the maximum allocated and physical capacity supported by the DataPod.
* **m.node configuration:** Determines the physical capacity available for storing data.
* **Storage architecture and cloud provider:** Determine the supported m.node configurations, scaling limits, and underlying cloud resources.
* **Flex cluster size:** Determines the total number of DataPods, c.nodes, and m.nodes the Flex environment can support.

Actual performance and usable capacity depend on workload characteristics, deployment topology, and cloud-provider limitations. Refer to the DataPod size and configuration limits documentation for current configuration-specific values.

## Evaluate cluster size

Flex supports small, medium, and large cluster configurations. The selected cluster size determines how many DataPods, c.nodes, and m.nodes can eventually be deployed within the Flex environment.

Cluster size is selected during deployment and can't be changed later. Plan the cluster for anticipated growth across the entire environment, not just the DataPods included in the initial deployment.

Cluster size also determines the address space that must be reserved for the deployment. Review the cloud-specific sizing and networking requirements before deploying Flex.

## Plan the maximum allocated capacity

Maximum allocated capacity represents the amount of logical data the DataPod can support before compression and deduplication are applied.

Since this limit can’t be changed after the DataPod is created, be sure to account for more than just the data you're migrating initially. Consider:

* Current logical size of your workloads
* Expected application and database growth
* Potential new workloads
* Snapshot retention requirements
* Copies created for development, testing, analytics, or recovery
* Replicated data maintained on the DataPod
* Temporary capacity required during migrations or other operations

Don't base your selected limit only on current consumption. Plan for the expected life of the DataPod and include sufficient room for workload growth and operational copies.

The selected maximum allocated capacity also affects the c.node configuration required for the DataPod. Validate your intended limit and node configuration with your Silk representative before deployment.

## Estimate physical capacity requirements

Physical capacity is consumed after compression and deduplication are applied and is determined by the DataPod's m.node configuration.

When estimating physical capacity requirements:

1. Determine the current logical size of your workloads.
2. Estimate logical data growth through your next planned capacity review or expansion.
3. Include snapshots, clones, replication targets, and other data copies in your evaluation.
4. Apply a conservative data-reduction estimate based on representative workload data.
5. Reserve physical capacity for growth and administrative operations.

The amount of data reduction achieved depends on the workload. Databases and copies containing repeated data may reduce differently than encrypted, pre-compressed, or highly unique datasets.

Snapshots and clone types also consume capacity differently. Full clones create independent copies of volume data, while thin clones share existing data and only consume additional physical capacity as new data is written. Account for the types of copies you expect to maintain, as well as how frequently their data will change.

Unlike maximum allocated capacity, physical capacity can be expanded by adding or changing m.nodes within the limits of the deployment profile, c.node configuration, storage architecture, and cloud provider.

## Maintain capacity headroom

Available physical capacity provides room for unexpected growth, changes in retention, and administrative operations.

Maintain headroom for:

* Workloads that grow faster than expected
* Changes to snapshot or retention policies
* Additional development, testing, or recovery operations
* Workloads that achieve less data reduction than anticipated
* Operations that require free physical capacity

For example, m.node live migration requires at least 20% free physical capacity, excluding the capacity of the m.node being removed.

The appropriate operating threshold depends on the environment and the operations you plan to perform. Work with your Silk representative to establish suitable capacity targets.

## Monitor capacity growth

Monitor both allocated and physical capacity because they identify different constraints:

* Growth in **allocated capacity** indicates that the DataPod is approaching its fixed logical capacity limit.
* Growth in **physical capacity** indicates that the DataPod is consuming the storage available from its m.nodes.
* If **physical capacity grows faster than allocated capacity**, new data may achieve less compression or deduplication than expected. The DataPod may require additional physical capacity sooner than projected.

You can review capacity information in the SDP Management Console and Silk Clarity. Use capacity trends to identify sustained growth and allow time to adjust retention policies, manage workload consumption, or expand physical capacity.

Volume group quotas can also help control logical growth by limiting the capacity individual workloads or groups of workloads can consume.

## Related resources

{% content-ref url="/spaces/jI1rjszhUJU6LG8J53d0/pages/jbwHJE9XlrTdPS1lXZgj" %}
[Clusters and DataPods](/learn/products-and-core-concepts/datapod-architecture/clusters-and-datapods.md)
{% endcontent-ref %}

{% content-ref url="/spaces/jI1rjszhUJU6LG8J53d0/pages/RACFGQWRzeDLCRkQE8tg" %}
[DataPod Deployment Profiles](/learn/products-and-core-concepts/datapod-architecture/datapod-deployment-profiles.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.silk.us/deploy/plan-your-deployment/plan-datapod-capacity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
