> 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/learn/products-and-core-concepts/datapod-architecture/datapod-deployment-profiles.md).

# DataPod Deployment Profiles

Compare DataPod deployment profiles and learn how each profile affects performance, capacity, cloud-resource requirements, and scaling options.

Silk DataPods support different configurations for different workload, performance, capacity, and cost requirements. Before deploying a DataPod, understand how its deployment profile affects the cloud resources, capacity ranges, performance characteristics, and scaling options available to you.

A deployment profile defines the DataPod's workload and storage model. However, it doesn't determine the final size of the DataPod. After selecting a profile, choose from the node types and capacity options the profile supports.

## Workload profile vs. storage type

When creating a DataPod, you select both a **workload profile** and a **storage type**. Together, these selections define the DataPod's **deployment profile**.

{% columns %}
{% column %}

### <i class="fa-square-sliders" style="color:$primary;">:square-sliders:</i>

**Workload profile** determines the supported c.node configurations, logical capacity options, and availability of read cache acceleration.
{% endcolumn %}

{% column %}

### <i class="fa-hard-drive" style="color:$primary;">:hard-drive:</i>

**Storage type** determines the m.node and d.node architecture used to provide physical capacity.
{% endcolumn %}
{% endcolumns %}

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

Some DataPod deployment profile and maximum allocated capacity cannot be changed after creation. Review your current requirements and anticipated growth with your Silk representative before deploying a DataPod.
{% endhint %}

VM Local Disks are supported across AWS, Azure, and Google Cloud. Managed Disks use Azure Premium SSD v2 (Pv2) and are available only on Azure.

The selected storage type can limit which workload profiles and c.node types are available. Flex displays compatible options as you configure the DataPod.

## Compare workload profiles

When creating a DataPod, select a workload profile based on performance characteristics, capacity requirements, and the resources available from your cloud provider.

<table><thead><tr><th width="133.29632568359375">Workload Profile</th><th width="215.6292724609375">Intended Use</th><th width="214.18505859375">Characteristics</th><th>Supported Cloud Providers</th></tr></thead><tbody><tr><td><strong>High Performance</strong></td><td>Most production workloads requiring balanced performance and scalability.</td><td>The default profile. Supports the standard production logical-capacity model and compatible c.node options.</td><td><ul><li>AWS</li><li>Azure</li><li>Google Cloud</li></ul></td></tr><tr><td><strong>Accelerated Performance</strong></td><td>Read-intensive or latency-intensive workloads requiring higher sustained performance.</td><td>Adds read cache to each c.node. The required VM configuration can increase cloud-resource and quota requirements.</td><td><ul><li>Azure</li><li>Google Cloud</li></ul></td></tr><tr><td><strong>Limited Capacity</strong></td><td>Smaller deployments that don't require the standard production logical-capacity range.</td><td>Supports lower logical-capacity configurations and is hidden by default in Flex.</td><td><ul><li>Azure</li><li>Google Cloud</li></ul></td></tr></tbody></table>

{% hint style="info" %}
**Enable Limited Capacity**

**Limited Capacity** is available only when **Allow limited logical capacity** is enabled in the advanced DataPod configuration options.
{% endhint %}

The selected profile determines which c.node and m.node configurations, capacity ranges, and scaling options are available. Supported options also vary by cloud provider, storage architecture, and available cloud resources.

### Accelerated Performance and read cache

Accelerated Performance is a DataPod configuration option that adds read cache to each c.node. The cache reduces repeated access to the capacity layer by serving frequently accessed data from the performance layer, which can improve read throughput and latency for read-intensive workloads.

The required c.node configuration for Accelerated Performance can increase cloud resource, quota, and infrastructure cost requirements. Actual performance benefits depend on the workload's access patterns.

## Select compatible node types

Flex presents supported c.node and m.node VM types for the selected workload profile, storage type, and cloud provider. When multiple options are available, Flex identifies the recommended node type and displays relevant resource or performance limitations.

This flexibility allows you to select compatible VM types based on workload requirements, cloud-resource availability, and cost. It can also provide alternatives when the preferred VM type or quota is unavailable in the target region.

Keep these configuration rules in mind:

* All c.nodes within a DataPod use the same VM type.
* The selected c.node type must support the workload profile and storage type.
* Supported VM-based m.node types can be combined within the same DataPod.
* Each m.node uses a single supported d.node VM type.
* VM Local Disk and Managed Disk m.nodes can't be combined in the same DataPod during standard configuration or scaling.

Flex also supports selecting a compatible m.node type when adding physical capacity.

## Evaluate workload and platform requirements

Consider the following factors when selecting a deployment profile and compatible node configuration:

<details>

<summary><strong>Workload performance</strong></summary>

Estimate expected IOPS throughput, latency, sustained bandwidth, and the balance of read and write activity. Read-intensive or latency-sensitive workloads may benefit from Accelerated Performance.

</details>

<details>

<summary><strong>Capacity and growth</strong></summary>

Confirm that the profile supports the required allocated capacity range and projected physical capacity expansion.

</details>

<details>

<summary><strong>Cloud resource availability</strong></summary>

Verify that compatible VM families, storage resources, and quota are available in the target cloud region.

</details>

<details>

<summary><strong>Cost</strong></summary>

Compare the cloud infrastructure required by your selected node types. Accelerated Performance and larger resource configurations can increase cloud costs.

</details>

<details>

<summary><strong>Sustained workload behavior</strong></summary>

Account for cloud-provider bandwidth limits and other infrastructure characteristics that may affect sustained performance.

</details>

{% hint style="warning" %}
**Confirm your configuration before deployment**

Validate the selected workload profile, storage type, node types, and intended capacity with your Silk representative before deploying the DataPod. Some related choices, including maximum allocated capacity, cannot be changed after deployment.
{% endhint %}

## Next steps

* [**Plan DataPod Capacity**](/deploy/plan-your-deployment/plan-datapod-capacity.md)**.** Estimate maximum allocated capacity, physical capacity requirements, and growth headroom.
* **Review DataPod limits.** Check current capacity, node, host, and scaling limits for supported DataPod configurations.
* **Plan your deployment.** Review the architecture, networking, permissions, quotas, and other requirements for your cloud provider.
* **Create a DataPod.** Select the workload profile, storage type, and compatible node configuration in Silk Flex.
* [**Contact Silk Support**](https://support.silk.us)**.** Get help selecting a configuration.


---

# 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/learn/products-and-core-concepts/datapod-architecture/datapod-deployment-profiles.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.
