Skip to content

Commit 37348d1

Browse files
committed
Adding more content, fixing storage threshold number
1 parent 3dc6fc2 commit 37348d1

File tree

1 file changed

+10
-5
lines changed

1 file changed

+10
-5
lines changed

articles/cosmos-db/merge.md

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -32,12 +32,17 @@ To check whether an Azure Cosmos DB account is eligible for the preview, you can
3232
:::image type="content" source="media/merge/merge-eligibility-check.png" alt-text="Merge eligibility check with table of all preview eligibility criteria":::
3333

3434
### How to identify containers to merge
35-
Containers that meet both of these criteria are likely to benefit from merging partitions:
36-
- Criteria 1: The current RU/s per physical partition is <3000 RU/s
37-
- Criteria 2: The current average storage in GB per physical partition is <35 GB
35+
Containers that meet both of these conditions are likely to benefit from merging partitions:
36+
- Condition 1: The current RU/s per physical partition is <3000 RU/s
37+
- Condition 2: The current average storage in GB per physical partition is <20 GB
38+
39+
Condition 1 often occurs when you have previously scaled up the RU/s (often for a data ingestion) and now want to scale down in steady state.
40+
Condition 2 often occurs when you delete/TTL a large volume of data, leaving unused partitions.
3841

3942
#### Criteria 1
40-
To determine the current RU/s per physical partition, from your Cosmos account, navigate to **Metrics**. Select the metric **Physical Partition Throughput** and filter to your database and container. Apply splitting by **PhysicalPartitionId**. For containers using autoscale, this will show the max RU/s currently provisioned on each physical partition. For containers using manual throughput, this will show the manual RU/s on each physical partition.
43+
To determine the current RU/s per physical partition, from your Cosmos account, navigate to **Metrics**. Select the metric **Physical Partition Throughput** and filter to your database and container. Apply splitting by **PhysicalPartitionId**.
44+
45+
For containers using autoscale, this will show the max RU/s currently provisioned on each physical partition. For containers using manual throughput, this will show the manual RU/s on each physical partition.
4146

4247
In the below example, we have an autoscale container provisioned with 5000 RU/s (scales between 500 - 5000 RU/s). It has 5 physical partitions and each physical partition has 1000 RU/s.
4348

@@ -54,7 +59,7 @@ Next, find the total number of physical partitions. This is the distinct number
5459

5560
Finally, calculate: Total storage in GB / number of physical partitions. In our example, we have an average of (74 GB / 5 physical partitions) = 14.8 GB per physical partition.
5661

57-
Based on criteria 1 and 2, our container is a candidate for merging partitions.
62+
Based on criteria 1 and 2, our container can potentially benefit from merging partitions.
5863

5964
### Merging physical partitions
6065

0 commit comments

Comments
 (0)