Is it possible to have 2 physical partitions instead of the default 10 in Azure Cosmos DB?

Is it possible to have 2 physical partitions instead of the default 10 in Azure Cosmos DB?

We switched to a partitioned collection in order to have better performance on aggregate queries. However, since we have 2,500 RU / s for the entire collection, this leaves us with 250 RU / s per physical partition (Cosmos DB automatically creates 10 physical partitions).

We would like to improve RU / s to a non-scaling RU / s partition for the entire collection. Thus, we need fewer partitions.

-Edit -

Azure support changed the default collection size to 20gb with two physical partitions for us. Thus, we have better performance per physical partition. Because the performance is set at the collection level and divided by the number of physical partitions.

The support also said that the partition cannot be resized, so the physical partition in azure kosmos db is tied to 10gb. When you need more memory, there is no other way than setting higher RU / s for your collection to maintain the same performance level for each partition.

+3


source to share


1 answer


Is it possible to have 2 physical partitions instead of the default 10 in Azure Cosmos DB?

The number of partitions is determined in the Cosmos DB database based on the storage size and the granted bandwidth of the container (collection (for a document), graphic, or table), and partition management is fully managed by Azure Cosmos DB. Once the collection is created, only THROUGHPUT (RU / s) is activated , which can be modified through the Azure portal. As Jesse Carter said, there is currently no direct way to control the number of physical partitions.



For detailed information on partitioning in Azure Cosmos DB, please see this article .

0


source







All Articles