Skip to content

Commit e750828

Browse files
committed
Adding autopilot throughput limitations
1 parent 306f862 commit e750828

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/cosmos-db/request-units.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Azure Cosmos DB supports many APIs, such as SQL, MongoDB, Cassandra, Gremlin, an
1616

1717
The cost of all database operations is normalized by Azure Cosmos DB and is expressed by *Request Units* (or RUs, for short). You can think of RUs per second as the currency for throughput. RUs per second is a rate-based currency. It abstracts the system resources such as CPU, IOPS, and memory that are required to perform the database operations supported by Azure Cosmos DB.
1818

19-
The cost to read a 1 KB item is 1 Request Unit (or 1 RU). A minimum of 10 RU/s are required to store 1 GB of data. All other database operations are similarly assigned a cost using RUs. No matter which API you use to interact with your Azure Cosmos container, costs are always measured by RUs. Whether the database operation is a write, read, or query, costs are always measured in RUs.
19+
The cost to read a 1 KB item is 1 Request Unit (or 1 RU). A minimum of 10 RU/s are required to store 1 GB of data. All other database operations are similarly assigned a cost using RUs. No matter which API you use to interact with your Azure Cosmos container, costs are always measured by RUs. Whether the database operation is a write, read, or query, costs are always measured in RUs.
2020

2121
The following image shows the high-level idea of RUs:
2222

0 commit comments

Comments
 (0)