Serverless movr usage

_includes/cockroachcloud/serverless-usage.md

@@ -1 +1 @@
-The best way to estimate your resource usage is to [enter a spend limit](serverless-cluster-management.html#edit-your-spend-limit) you're comfortable with and run your workload. You can see the RUs and storage your cluster has used in the **Usage this month** section of the [**Cluster Overview**](serverless-cluster-management.html#view-cluster-overview) page. Once enough usage data is available, you can also see a graph of your monthly resource usage and recommended spend limit on the [**Edit cluster**](serverless-cluster-management.html#edit-your-spend-limit) page.
+The best way to estimate your resource usage is to [enter a spend limit](serverless-cluster-management.html#edit-your-spend-limit) you're comfortable with and run your workload. You can see the RUs and storage your cluster has used in the **Usage this month** section of the [**Cluster Overview**](serverless-cluster-management.html#view-cluster-overview) page. Once enough usage data is available, you can also see a graph of your monthly resource usage and recommended spend limit on the [**Edit cluster**](serverless-cluster-management.html#edit-your-spend-limit) page. For a tutorial on estimating your {{ site.data.products.serverless }} usage using a sample workload, see [Estimate Serverless Usage with MovR](serverless-movr.html).

_includes/v21.2/sidebar-data/get-started.json

@@ -91,6 +91,12 @@
             "/${VERSION}/deploy-app-gcr.html"
           ]
         },
+        {
+          "title": "Estimate Serverless Usage with MovR",
+          "urls": [
+            "/cockroachcloud/serverless-movr.html"
+          ]
+        },
         {
           "title": "Netlify",
           "urls": [

_includes/v22.1/sidebar-data/get-started.json

@@ -91,6 +91,12 @@
             "/${VERSION}/deploy-app-gcr.html"
           ]
         },
+        {
+          "title": "Estimate Serverless Usage with MovR",
+          "urls": [
+            "/cockroachcloud/serverless-movr.html"
+          ]
+        },
         {
           "title": "Netlify",
           "urls": [

cockroachcloud/create-a-serverless-cluster.md

@@ -33,7 +33,7 @@ Every cluster starts with 10M RUs of free [burst capacity](architecture.html#coc
 
 If you set 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.
 
-{% include cockroachcloud/serverless-usage.md %} For more information, see [Planning your cluster](plan-your-cluster.html).
+{% include cockroachcloud/serverless-usage.md %}
 
 {{site.data.alerts.callout_info}}
 Regardless of whether you set a spend limit, [adding billing information](billing-management.html) for your organization allows you to use [cloud storage for bulk operations](run-bulk-operations.html). Organizations without billing information are limited to [using `userfile` storage for bulk operations](run-bulk-operations.html).

cockroachcloud/serverless-movr.md

@@ -0,0 +1,111 @@
+---
+title: Estimate Serverless Usage with MovR
+summary: Run the MovR sample application to estimate RU usage in CockroachDB Serverless.
+toc: true
+referral_id: docs_serverless_movr
+docs_area: get_started
+---
+
+This tutorial shows you how to initialize and run the [MovR](../{{site.versions["stable"]}}/movr.html) workload on a {{ site.data.products.serverless }} cluster, then use the [Request Unit](serverless-faqs.html#what-is-a-request-unit) consumption data to estimate a sufficient budget for the MovR workload.
+
+{{site.data.alerts.callout_info}}
+The cost estimation tool in [Step 5](#step-5-view-your-usage-costs) is not currently available for organizations billed through Credits.
+{{site.data.alerts.end}}
+
+## Overview
+
+[MovR](../{{site.versions["stable"]}}/movr.html) is a fictional company that offers users a platform for sharing vehicles, like scooters, bicycles, and skateboards, in select cities across the United States and Europe. You want to use {{ site.data.products.serverless }} to run MovR's high-growth, variable workload. You decide to test out a sample workload to see how it will perform and how much it will cost to run.
+
+## Before you begin
+
+- Make sure you have already [installed CockroachDB](../{{site.versions["stable"]}}/install-cockroachdb.html).
+- [Create a {{ site.data.products.serverless }} cluster](create-a-serverless-cluster.html).
+
+## Step 1. Create the `movr` database
+
+1. Navigate to your cluster's [**Databases** page](databases-page.html).
+1. Click the **Add Database** button.
+1. Enter `movr` as the database name. 
+1. Click **Create**.
+
+## Step 2. Get the cluster connection string
+
+1. On the cluster's [**Overview** page](cluster-overview-page.html), click **Connect**.
+1. Select `movr` from the **Database** dropdown.
+1. Select **General connection string** from the **Select option/language** dropdown.
+1. Copy the connection string displayed and save it in a secure location.
+
+## Step 3. Load the `movr` workload
+
+Exit the SQL shell and [load the `movr` dataset](../{{site.versions["stable"]}}/cockroach-workload.html#movr-workload) using the new connection string:
+
+  {% include copy-clipboard.html %}
+  ~~~ shell
+  cockroach workload init movr \
+  "postgresql://<username>:<password>@serverless-host>:26257/movr?sslmode=verify-full&options=--cluster%3D<routing-id>"
+  ~~~
+
+  The following error may occur but will not affect the rest of this tutorial: `pq: unimplemented: operation is unsupported in multi-tenancy mode`.
+
+## Step 4. Run the workload
+
+Run the `movr` workload for 30 minutes using the same SQL connection string as before:
+
+  {% include copy-clipboard.html %}
+  ~~~ shell
+  cockroach workload run movr \
+  --duration=30m \
+  "postgresql://<username>:<password>@serverless-host>:26257/movr?sslmode=verify-full&options=--cluster%3D<routing-id>"
+  ~~~
+
+  You'll see per-operation statistics print to standard output every second:
+
+  ~~~
+  _elapsed___errors__ops/sec(inst)___ops/sec(cum)__p50(ms)__p95(ms)__p99(ms)_pMax(ms)
+      1.0s        0           31.9           32.0      0.5      0.6      1.4      1.4 addUser
+      1.0s        0            6.0            6.0      1.2      1.4      1.4      1.4 addVehicle
+      1.0s        0           10.0           10.0      2.2      6.3      6.3      6.3 applyPromoCode
+      1.0s        0            2.0            2.0      0.5      0.6      0.6      0.6 createPromoCode
+      1.0s        0            9.0            9.0      0.9      1.6      1.6      1.6 endRide
+      1.0s        0         1407.5         1407.8      0.3      0.5      0.7      4.1 readVehicles
+      1.0s        0           27.0           27.0      2.1      3.1      4.7      4.7 startRide
+      1.0s        0           86.8           86.9      4.7      8.4     11.5     15.2 updateActiveRides
+      2.0s        0           26.0           29.0      0.5      1.1      1.4      1.4 addUser
+      2.0s        0            8.0            7.0      1.2      2.8      2.8      2.8 addVehicle
+      2.0s        0            2.0            6.0      2.6      2.8      2.8      2.8 applyPromoCode
+      2.0s        0            0.0            1.0      0.0      0.0      0.0      0.0 createPromoCode
+      2.0s        0            6.0            7.5      0.8      1.7      1.7      1.7 endRide
+      2.0s        0         1450.4         1429.1      0.3      0.6      0.9      2.6 readVehicles
+      2.0s        0           17.0           22.0      2.1      3.3      5.5      5.5 startRide
+      2.0s        0           59.0           72.9      6.3     11.5     11.5     14.2 updateActiveRides
+  ...
+  ~~~
+
+  After the specified duration (30 minutes in this case), the workload will stop and you'll see totals printed to standard output:
+
+  ~~~
+  _elapsed___errors_____ops(total)___ops/sec(cum)__avg(ms)__p50(ms)__p95(ms)__p99(ms)_pMax(ms)__result
+   1800.1s        0           5061            2.8    355.9    209.7   1073.7   2684.4   5368.7  
+  ~~~
+
+## Step 5. View your usage costs
+
+1. In the **Usage this month** section of your cluster's [**Overview** page](cluster-overview-page.html), click **Estimate usage cost**.
+1. Select **Past 30 minutes** as the time frame.
+
+    Your **Monthly estimate for this workload** is displayed.
+
+The **Spend over time** graph will be populated with the RU and storage you used running the `movr` workload, as well as any other usage you had over the last 30 minutes. The **Monthly estimate for this workload** is calculated based on this usage. Ideally your spend limit should be higher than this estimate to allow for any variability in the workload over the month. A cluster's spend limit is meant to prevent you from accidentally spending more than you are comfortable with, not to be the most accurate prediction of your costs.
+
+## Next steps
+
+The MovR team can monitor their usage in the {{ site.data.products.db }} Console, and they will receive [email alerts](alerts-page.html#configure-alerts) when the cluster approaches 50%, 75%, and 100% of its spend limit. If their workload grows and they reach the limits of the {{ site.data.products.serverless }} free offering, they can then [set a spend limit](serverless-cluster-management.html#edit-your-spend-limit).
+
+To estimate the actual costs for your cluster, you should run your real workload and gather usage data. You can always [edit your spend limit](serverless-cluster-management.html) if your initial estimate turns out to be inaccurate or your budget changes.
+
+## See also
+
+- [Serverless Performance Benchmarking](serverless-benchmarking.html)
+- [Manage a CockroachDB Serverless Cluster](serverless-cluster-management.html)
+- [The MovR Example Application](../stable/movr.html)
+- [Example Apps](../stable/example-apps.html)