Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
RU calculation from ItemResponse
See original GitHub issueHello, we’re kind of confused by tracking the RU spent with RequestCharge from ItemResponse using current SDK v3, we’ve referred the documentation via here, however, in our scenario, we found our RU from reading one document is always 1…so for reading 80 items the total RU is 80…And it never changes no matter how many documents existed in our collection or if our document schema changes… Which doesn’t seem to be correct number compared to use SQL Query within azure portal.
Here is a screenshot of our code implementation and output result:
Thank you very much for your help!
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
A point read of one item of < 1024b is literally defined as being 1 RU (1 RU per KiB or part thereof), and intentionally is not affected by amount of records etc. Perhaps you’re comparing with charges for queries? even a query that yields a single document with a basic query has a completely different set of charges - definitely strongly recommend reading the charging model docs - its the real instructions on how to best use CosmosDB.
CosmosExceptions have RU counts as a property too (one reason being if you invoke a stored proc etc., it can incur plenty cost before failing).