Skip to content

Commit f35ba75

Browse files
committed
throughput formula updated
1 parent 92193fc commit f35ba75

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

articles/cosmos-db/nosql/how-to-change-capacity-mode.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,14 +14,15 @@ ms.custom: build-2024
1414

1515
[!INCLUDE[NoSQL](../includes/appliesto-nosql.md)]
1616

17-
Azure Cosmos DB allows a user to change the capacity mode of an account from serverless to provisioned capacity. Changing from serverless to provisioned capacity mode converts all containers within the account to manual provisioned throughput containers in-place. The containers' throughput is determined according to the following formula.
17+
Azure Cosmos DB allows a user to change the capacity mode of an account from serverless to provisioned capacity. Changing from serverless to provisioned capacity mode converts all containers within the account to manual provisioned throughput containers in-place. The containers' throughput is approximately determined according to the following formula.
1818

19-
`Throughput(RU/s) = max(5000, StorageInGB * 10)`
19+
`Throughput(RU/s) = max(5000, number of partitions (physical) * 1000)`
2020

2121
Users can also change the throughput or provisioning mode from manual to autoscale once the migration is complete.
2222

2323
>[!Caution]
24-
>This is an irreversible operation. Once migrated, the capacity mode can't be changed back to serverless.
24+
> This is an irreversible operation. Once migrated, the capacity mode can't be changed back to serverless.
25+
> The throughput calculation and default provisioning mode (manual) is subject to change in future.
2526
2627
## Getting started
2728

@@ -39,7 +40,7 @@ Follow the steps below to change the capacity mode using Azure portal.
3940

4041
4. Once the migration is complete, the capacity mode will be changed to **provisioned capacity**.
4142

42-
> [!Note]
43+
>[!Note]
4344
> There are no SLA's associated with the duration of the capacity mode change.
4445
> Users cannot execute any management operation while the migration is in progress. However, the containers can be accessed as usual by any client application.
4546

0 commit comments

Comments
 (0)