-
Notifications
You must be signed in to change notification settings - Fork 468
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Serverless movr usage #13354
base: main
Are you sure you want to change the base?
Serverless movr usage #13354
Conversation
Files changed:
|
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify site settings. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status:
complete! 0 of 0 LGTMs obtained (waiting on @emily-horing and @gemma-shay)
cockroachcloud/serverless-movr.md
line 89 at r4 (raw file):
3. Multiply your usage over one minute by the number of minutes in a month (43800) to estimate how many RUs the workload would use in a month. For example, if you used 1800 RUs: 1800 RUs/min * 43800 min = 78,840,000 RUs. 3. Calculate how many additional RUs you will need. The workload is estimated to use about 79 million RUs per month, and you are given 26.5 million RUs for free, so you need to budget for about 52.5 million additional RUs.
Currently, we give 10M RUs free per month + 100 RU/s for free. That adds to more than 250M RUs per month (depending on # days in the month). Where did you get the 26.5M RU number?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status:
complete! 0 of 0 LGTMs obtained (waiting on @andy-kimball and @emily-horing)
cockroachcloud/serverless-movr.md
line 89 at r4 (raw file):
Previously, andy-kimball (Andy Kimball) wrote…
Currently, we give 10M RUs free per month + 100 RU/s for free. That adds to more than 250M RUs per month (depending on # days in the month). Where did you get the 26.5M RU number?
Sorry, not sure where that came from. I think I might have been pulling a random number from a cluster in the console by accident. Fixed that step and added a placeholder for Emily's suggestion (another step for re-calculating the budget with an expanded user base), but I'm not sure how to simulate that growth with movr.
@emily-horing can you take a look at this when you have time? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status:
complete! 0 of 0 LGTMs obtained (waiting on @andy-kimball, @emily-horing, and @gemma-shay)
cockroachcloud/serverless-movr.md
line 2 at r5 (raw file):
--- title: Estimate Serverless Usage with MovR
overall: if we're using movr as an example, I think we should narrate more as a story that you can follow along with rather than plain instructions. personal preference perhaps but it feels more relatable to be like "the movr team wants to use serverless to run their high-growth, variable workload, so they test out a sample workload to see how it will perform and what it will cost to run". I want our users to see the example and feel like it's a similar scenario to what they are going through. wdyt?
cockroachcloud/serverless-movr.md
line 3 at r5 (raw file):
--- title: Estimate Serverless Usage with MovR summary: Run the MovR sample application to estimate RU usage in CockroachDB Serverless.
side note: we may add a small feature that helps with estimation on an existing cluster w previous usage. I'll keep you tagged on that.
cockroachcloud/serverless-movr.md
line 9 at r5 (raw file):
--- This tutorial shows you how to initialize and run the MovR workload on a {{ site.data.products.serverless }} cluster, then use your Request Unit consumption data to estimate a sufficient budget for your cluster.
To me this sounds like running movr will help you estimate your own workload, but that's not exactly a fair comparison. I think this should say something like "this example walks you through how to estimate RU costs for an app using the movr workload".
Also, it would make sense to me to combine this example with generic docs on "how to estimate". Eg:
Section 1: How to estimate your workload --> generic instructions with notes on how to interpret RU charts/overview page
Section 2: Movr Example. --> walk through of how this can be done with movr as the "real" example
cockroachcloud/serverless-movr.md
line 15 at r5 (raw file):
Make sure you have already [installed CockroachDB](../{{site.versions["stable"]}}/install-cockroachdb.html). ## Step 1. Create a {{ site.data.products.serverless }} cluster
Nit: let's move this. to "before you begin". Just say "you have created a new cluster" with a link to where we give detailed instructions elsewhere.
cockroachcloud/serverless-movr.md
line 19 at r5 (raw file):
{% include cockroachcloud/quickstart/create-a-free-cluster.md %} ## Step 2. Set up your cluster connection
Nit: "get" cluster connection seems more accurate than "set up".
cockroachcloud/serverless-movr.md
line 25 at r5 (raw file):
## Step 3. Load the `movr` workload Load the dataset using the SQL connection string you copied in [Step 2](#step-2-set-up-your-cluster-connection):
nit: sql connection made me thinks cockroach sql
--> just connection is better
cockroachcloud/serverless-movr.md
line 95 at r5 (raw file):
Let's say Movr is planning to expand, and you expect to have three times as many users this month, so you need to estimate a new budget. 1. PLACEHOLDER
I was originally thinking we can just make up a story + some math here, but annoyingly we give away too much to easily cross the paid threshold! Do we have anyway to make movr do more txns? it would be cool if we could specify that, run it again. So the message would be "simulate your expected behavior". Alternatively, I would be ok to get rid of this section.
we could say something like 'movr has an exciting growth opportunity and expects to quadruple its user base in 3 months. This will linearly increase Movr's workload by 4x, with both reads and writes scaling proportionately. MovR now expects to use ~316M RUs and x storage in the future (79M*4)' but i'm not sure that that's actually useful? maybe instead we can just say "next steps" --> movr monitors usage periodically and can set a spend limit once they receive and alert that their cluster is nearing their free limits
commit 480c8e5 Merge: e468ceb 232bf26 Author: Gemma Shay <[email protected]> Date: Thu Jun 23 16:14:50 2022 -0400 Merge branch 'master' into DOC-2827-serverless-movr merge master commit e468ceb Author: Gemma Shay <[email protected]> Date: Thu Jun 23 15:52:51 2022 -0400 emily review and create database commit 898fc63 Author: Gemma Shay <[email protected]> Date: Thu Jun 9 15:39:42 2022 -0400 andy review and emily follow up suggestion draft commit f8b6f77 Author: Gemma Shay <[email protected]> Date: Thu Jun 2 18:09:36 2022 -0400 calculation commit b98ca17 Merge: f3cbd9e 43c5144 Author: Gemma Shay <[email protected]> Date: Thu Jun 2 17:40:25 2022 -0400 Merge branch 'master' into DOC-2827-serverless-movr commit f3cbd9e Author: Gemma Shay <[email protected]> Date: Tue Mar 29 14:05:02 2022 -0400 edit commit b3be052 Author: Gemma Shay <[email protected]> Date: Tue Mar 29 13:42:06 2022 -0400 edit and formatting commit 7402854 Merge: 1bd49ae 7118111 Author: Gemma Shay <[email protected]> Date: Mon Mar 28 14:30:08 2022 -0400 Merge branch 'DOC-2827-serverless-movr' of https://github.com/cockroachdb/docs into DOC-2827-serverless-movr commit 1bd49ae Author: Gemma Shay <[email protected]> Date: Mon Mar 28 14:30:04 2022 -0400 link fix commit 7118111 Merge: 32d6766 43bd4b5 Author: Gemma Shay <[email protected]> Date: Fri Mar 25 14:32:40 2022 -0400 Merge branch 'master' into DOC-2827-serverless-movr commit 32d6766 Author: Gemma Shay <[email protected]> Date: Fri Mar 25 14:30:40 2022 -0400 draft commit 69ad3c6 Author: Gemma Shay <[email protected]> Date: Thu Mar 24 13:17:42 2022 -0400 draft commit 0b30677 Author: Gemma Shay <[email protected]> Date: Mon Mar 14 11:57:19 2022 -0400 draft squashh
480c8e5
to
54fd2e6
Compare
e25e8fe
to
13fdc99
Compare
13fdc99
to
79d6a57
Compare
merge master
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gemma I wrote some suggestions that I think would improve it - as discussed I'm OOO next week so ofc feel free to save these edits for after the eng/product review round
cockroachcloud/serverless-movr.md
Outdated
|
||
1. Multiply your usage over one minute by the number of minutes in a month (43800) to estimate how many RUs the workload would use in a month. For example, if you used 1800 RUs: 1800 RUs/min * 43800 min = 78,840,000 RUs. | ||
|
||
1. Calculate your budget. The workload is estimated to use about 79 million RUs per month, and you are given up to 250M free RUs per month, so the free {{ site.data.products.serverless }} offering should be sufficient for your usage. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this may be about a technical point that I'm not qualified on but I'd much rather read "you are given 250M free RUs" than "up to" since that sounds like a qualification / admission that some months I might not get the full 250M.
even though I assume you mean only that I get N million and 0 < N < 250
, I think "up to" introduces a question even if it does not mean to
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@emily-horing thoughts?
…chdb/docs into DOC-2827-serverless-movr
merge master
https://cockroachlabs.atlassian.net/browse/DOC-2827
https://cockroachlabs.atlassian.net/browse/DOC-4836