When you understand the factors that affect RU charges and your application's throughput requirements, you can run your application cost effectively. You can examine the response header to track the number of RUs consumed by any database operation. To manage and plan capacity, Azure Cosmos DB ensures that the number of RUs for a given database operation over a given dataset is deterministic. The following image shows the high-level idea of RUs: Whether the database operation is a write, point read, or query, costs are always measured in RUs. No matter which API you use to interact with your Azure Cosmos DB container, RUs measure the actual costs of using that API. All other database operations are similarly assigned a cost using RUs. The cost to do a point read (fetching a single item by its ID and partition key value) for a 1-KB item is one Request Unit (or one RU). Request unit is a performance currency abstracting the system resources such as CPU, IOPS, and memory that are required to perform the database operations supported by Azure Cosmos DB. Each database operation consumes system resources based on the complexity of the operation.Īzure Cosmos DB normalizes the cost of all database operations using Request Units (or RUs, for short). These operations range from simple point reads and writes to complex queries. Each API has its own set of database operations. Azure Cosmos DB supports many APIs, such as SQL, MongoDB, Cassandra, Gremlin, and Table.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |