Add Function to Set Collection Throughput #3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have added a new function (and some supporting functions) that allow R coders to set the CosmosDB collection throughput from within their R code.
This can help R users be more efficient with their RU's and save money when using Azure. For example, if you're using CosmosDB for cold storage of some data, you can leave the collection set at the lowest throughput (400 RU's). If you want to query the collection, your R code can turn up the throughput right before you run the query (so it will perform faster). Then, once it's done, your R script can immediately scale it back down.
Hopefully this will help our customers realize the promise of cloud computing: Pay only for what you use.