CC Serverless #10900
Merged
CC Serverless #10900
Conversation
This file contains 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
|
This change is |
|
✔️ Netlify Preview 🔨 Explore the source changes: 0197bd2 🔍 Inspect the deploy log: https://app.netlify.com/sites/cockroachdb-docs/deploys/616a106d64d6c90008a811ee 😎 Browse the preview: https://deploy-preview-10900--cockroachdb-docs.netlify.app |
|
cc: @ianjevans |
amruss
reviewed
Oct 11, 2021
jramos-crl
reviewed
Oct 11, 2021
kannanlakshmi
requested changes
Oct 15, 2021
|
|
||
| You can set your spend limit higher to maintain a high level of performance with larger workloads. If you have a spend limit, your cluster will not be throttled to baseline performance once you use all of your free earned RUs. Instead, it will continue to use burst performance as needed until you reach your spend limit. You will only be charged for the resources you use up to your spend limit. If you reach your spend limit, your cluster will revert to the baseline performance of 100 RUs per second. | ||
|
|
||
| For example, you have an application that processes sensor data at the end of the week. Most of the week it handles only occasional read requests, and spends under the 100 RUs per second baseline. At the end of the week the sensors send in their data to the application, requiring a burst over the 100 RUs per second baseline. When the cluster requires more than 100 RUs per second to cover the burst, it first spends the earned RUs from the previous week. If the burst requires more RUs than were earned the previous week, the cluster will spend RUs to cover the burst, up to your maximum spend limit. If you reach your spend limit at any point during the month, the cluster will continue to earn RUs during lower load periods and spend earned RUs during bursts, but after using the earned RUs during bursts it will not scale up beyond the 100 RUs per second baseline. |
There was a problem hiding this comment.
This example is confusing as written. I think its bc its not clear if this cluster has a spend limit > $0. I recommend adding an example with $0 spend and one that's more than $0 spend to illustrate what happens when they use up their burst capacity.
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Updated docs for serverless