This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(118.4, 67%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAC%3C/text%3E%3C/svg%3E)
We migrated our application from Table Storage to Cosmos DB Table API.
After the migration, we discovered that queries against any collection that are only against Partition Key take a lot of time to run . For example this query:
took 5 minutes to run and 5k RUs on the successful request but it generated lots of 429) while this query:
ran in 0.695 miliseconds and request charge was 5.72 RUs.
We tried several things on the indexing part (although, I thought indexing will work out of the box like Storage does).
]4
Could someone explain this behavior?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 10%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKM%3C/text%3E%3C/svg%3E)
@Andrei Corovei Welcome to Microsoft Q&A forums.
5 minutes and 5K RU's to retrieve 2 records is definitely not an expected behavior even when you do not specify the RowKey.
Are you seeing this consistently?
What happens when you consume the same from a client sdk?
Yes, we ended up investigating with Fiddler and DataExplorer to nail down the queries that do not work as expected from the client sdk.
Same experience from client SDK, UI pages that have as backend a query against partition key take a very long time to load generating several 429 until the request in processed.
Do you have any updates on the topic?
@Andrei Corovei ·429 Error code means "Too many requests"
Requests per second on the Cosmos account are exceeding the throughput you have provisioned.
Please consider increasing the provisioned throughput and you should see the error disappear.
Increasing the RUs will only increase the costs and not solve the root issue. In fact, we have increased the RUs but the query still runs in more than 5 minutes.
The problem is quite basic: querying based on partition key should return the results fast (in our case partition contain 10-12 records, max 100).
Anyways, we will continue the discussion in a support ticket.