|
| 1 | +--- |
| 2 | +title: Azure Cosmos DB Serverless 1-TB container (preview) |
| 3 | +description: Learn more about Serverless 1-TB container. |
| 4 | +author: richagaur |
| 5 | +ms.author: richagaur |
| 6 | +ms.service: cosmos-db |
| 7 | +ms.topic: conceptual |
| 8 | +ms.date: 12/01/2022 |
| 9 | +ms.reviewer: dech |
| 10 | +--- |
| 11 | + |
| 12 | +# Azure Cosmos DB Serverless 1-TB container (preview) |
| 13 | + |
| 14 | +[!INCLUDE[NoSQL, MongoDB, Cassandra, Gremlin, Table](includes/appliesto-nosql-mongodb-cassandra-gremlin-table.md)] |
| 15 | + |
| 16 | +Azure Cosmos DB serverless 1-TB container (preview) allows you to take advantage of serverless offering with up-to 1 TB of storage size for a container. You can now store up-to 1 TB of data in a serverless container. |
| 17 | + |
| 18 | +## Changes in Request Unit |
| 19 | + |
| 20 | +Azure Cosmos DB serverless 1-TB container provides you 5000 RU/s for a container. However, if your workload increases beyond 250 GB or more than five partitions, whichever is earlier, then the request units grow linearly with number of underlying physical partitions created in the container. Beyond 5 physical partitions, with every addition of a new physical partition, 1000 RU/s are added to the container's maximum throughput capacity. |
| 21 | + |
| 22 | +To understand request unit growth with storage, lets look at the table below. |
| 23 | + |
| 24 | +| Maximum storage | Minimum physical partitions | RU/s per container | RU/s per physical partition |
| 25 | +|:---:|:---:|:---:|:---:| |
| 26 | +|<=50 GB | 1 | 5000 | 5000 | |
| 27 | +|<=100 GB | 2 | 5000 | 2500 | |
| 28 | +|<=150 GB | 3 | 5000 | 1666 | |
| 29 | +|<=200 GB | 4 | 5000 | 1250 | |
| 30 | +|<=250 GB | 5 | 5000 | 1000 | |
| 31 | +|<=300 GB | 6 | 6000 | 1000 | |
| 32 | +|<=350 GB | 7 | 7000 | 1000 | |
| 33 | +|<=400 GB | 8 | 8000 | 1000 | |
| 34 | +|.........|...|......|......| |
| 35 | +|<= 1 TB | 20 | 20000| 1000 | |
| 36 | + |
| 37 | +Note: The request units can increase beyond 20000 RU/s for a serverless 1-TB container if more than 20 partitions are created in the container. It depends on the distribution of logical partition keys in your serverless 1-TB container. |
| 38 | + |
| 39 | +## How to get started |
| 40 | + |
| 41 | + To get started with serverless 1-TB container, register the *"Azure Cosmos DB Serverless 1 TB Container Preview"* [preview feature in your Azure subscription](../azure-resource-manager/management/preview-features.md). After the request is approved, all existing and future serverless accounts in the subscription will be able to use containers with size up to 1 TB. |
| 42 | + |
| 43 | +:::image type="content" source="media/serverless/enable-1-tb-preview.png" alt-text="Screenshot of serverless 1-TB container in Preview Features page in Subscription overview in Azure portal."::: |
| 44 | + |
| 45 | + |
| 46 | +To check whether an Azure Cosmos DB account is enabled for the serverless 1-TB container preview, you can use the built-in status checker in the Azure portal. From your Azure Cosmos DB account overview page in the Azure portal, navigate to Diagnose and solve problems -> Account Administration -> Serverless. On this page, you can check the status of preview on your serverless account. |
| 47 | + |
| 48 | +:::image type="content" source="media/serverless/diagnose-and-solve-account-admin.png" alt-text="Screenshot of Diagnose and Solve tab and issue categories in Azure portal."::: |
| 49 | + |
| 50 | +:::image type="content" source="media/serverless/serverless-1tb-status-check.png" alt-text="Screenshot of serverless 1-TB container status check insight in Azure portal."::: |
| 51 | + |
| 52 | +## Next steps |
| 53 | + |
| 54 | +- Learn more about [serverless](serverless.md) |
| 55 | +- Learn more about [request units.](request-units.md) |
| 56 | +- Trying to decide between provisioned throughput and serverless? See [choose between provisioned throughput and serverless.](throughput-serverless.md) |
0 commit comments