From e0a03fcb853135ebd716bf7d7342742128fd9a10 Mon Sep 17 00:00:00 2001 From: Matt Linville Date: Sat, 21 Sep 2024 14:56:39 -0700 Subject: [PATCH 01/16] [DOC-10386][DOC-11063] Update Plan a Standard Cluster, Cloud landing page --- .../basic-cluster-management.md | 6 +- .../cockroachcloud/cluster-management.md | 6 +- src/current/cockroachcloud/index.md | 242 +++++++++++++++++- .../cockroachcloud/plan-your-cluster.md | 180 +++++-------- 4 files changed, 305 insertions(+), 129 deletions(-) diff --git a/src/current/cockroachcloud/basic-cluster-management.md b/src/current/cockroachcloud/basic-cluster-management.md index 717a7e99479..1fba2212e39 100644 --- a/src/current/cockroachcloud/basic-cluster-management.md +++ b/src/current/cockroachcloud/basic-cluster-management.md @@ -35,11 +35,13 @@ The monthly cost estimate is calculated using simple extrapolation that assumes ## Edit cluster capacity -On the **Overview** page, you can edit your resource limits. Changes apply to the current and future billing cycles. For more details, refer to [Plan a CockroachDB {{ site.data.products.basic }} cluster]({% link cockroachcloud/plan-your-cluster-basic.md %}). +The price-performance characteristics of CockroachDB {{ site.data.products.basic }} vary significantly depending on the workload. It can be difficult to estimate a workload's compute requirements in advance. To increase or decrease a cluster's capacity: 1. In the **Capacity used this month** section of your cluster's [**Overview** page]({% link cockroachcloud/cluster-overview-page.md %}), click **Update capacity**. -1. On the **Capacity** page, set the configure the new resource limits. In the sidebar, click **Update cluster**. +1. On the **Capacity** page, edit the resource limits. In the sidebar, click **Update cluster**. + +Changes apply to the current and future billing cycles. For more details, refer to [Plan a CockroachDB {{ site.data.products.basic }} cluster]({% link cockroachcloud/plan-your-cluster-basic.md %}). ## Edit regions diff --git a/src/current/cockroachcloud/cluster-management.md b/src/current/cockroachcloud/cluster-management.md index cd06b094058..30f75ec77fd 100644 --- a/src/current/cockroachcloud/cluster-management.md +++ b/src/current/cockroachcloud/cluster-management.md @@ -38,6 +38,8 @@ From the **Overview** page, you can connect to your cluster. For more informatio ## Edit cluster capacity +The price-performance characteristics of CockroachDB {{ site.data.products.standard }} vary significantly depending on the workload. It can be difficult to estimate a workload's compute requirements in advance. To increase or decrease a cluster's provisioned capacity: + To edit your cluster's capacity: 1. Navigate to the cluster's **Overview** page. @@ -46,11 +48,13 @@ To edit your cluster's capacity: 1. Enter the desired number of request units per second or use the slider to increase or decrease the request units per second. {{site.data.alerts.callout_success}} - You can decrease the provisioned capacity only three times within a 7-day period. + You can decrease the provisioned capacity only three times within a 7-day period. You can increase the provisioned capacity at any time. {{site.data.alerts.end}} 1. In the sidebar, verify the new estimated cost for the cluster and click **Update cluster**. +To learn more, refer to [Plan a CockroachDB {{ site.data.products.standard }} cluster]({% link plan-your-cluster.md %}#provisioned-capacity). + ## Manage cluster upgrades By default, major-version and patch upgrades are automatically applied to CockroachDB {{ site.data.products.standard }} clusters. To control when a cluster is upgraded to a new major version, you can disable automatic major-version upgrades. Patch upgrades are always applied automatically. diff --git a/src/current/cockroachcloud/index.md b/src/current/cockroachcloud/index.md index d53853302ea..0ddc0afc858 100644 --- a/src/current/cockroachcloud/index.md +++ b/src/current/cockroachcloud/index.md @@ -1,13 +1,246 @@ --- -title: CockroachDB Cloud Docs -summary: CockroachDB Cloud is a fully hosted and fully managed service created and owned by Cockroach Labs that makes deploying, scaling, and managing CockroachDB effortless. -toc: false -contribute: false +title: CockroachDB Cloud docs +summary: Learn more about CockroachDB Cloud, a fully-managed service created and owned by Cockroach Labs that makes deploying, scaling, and managing CockroachDB effortless. +toc: true +contribute: true cta: false homepage: true docs_area: --- +## Overview + +CockroachDB {{ site.data.products.cloud }} is a fully-managed service run by Cockroach Labs, which simplifies deployment and management of CockroachDB deployments. This page provides an introduction to CockroachDB {{ site.data.products.cloud }} provides an overview of each type of cluster: CockroachDB {{ site.data.products.standard }}, CockroachDB {{ site.data.products.basic }}, and CockroachDB {{ site.data.products.advanced }}. + +To get started right away, you can [sign up for a CockroachDB {{ site.data.products.cloud }} account](https://cockroachlabs.cloud) and [create a cluster]({% link cockroachcloud/create-your-cluster.md %}) using [trial credits]({% link cockroachcloud/billing-management.md %}#view-credits-balance). + +## Plans + +When you create a cluster in CockroachDB {{ site.data.products.cloud }}, you select its plan. A CockroachDB {{ site.data.products.cloud }} organization can include clusters of each plan. This section provides an overview of each plan. For a more detailed comparison, refer to [Compare plans](#compare-plans). + +- **CockroachDB {{ site.data.products.basic }}**: TODO + +- **CockroachDB {{ site.data.products.standard }}**: TODO + +- ** CockroachDB {{ site.data.products.advanced }}**: TODO + +## Compare plans + +This section summarizes key details about each plan to help you make the best choice for each cluster and its workload. For more details, refer to: + +- [Plan a CockroachDB {{ site.data.products.basic }} cluster]({% link cockroachcloud/plan-a-basic-cluster.md %}) +- [Plan a CockroachDB {{ site.data.products.standard }} cluster]({% link cockroachcloud/plan-your-cluster.md %}) +- [Plan a CockroachDB {{ site.data.products.advanced }} cluster]({% link cockroachcloud/plan-an-advanced-cluster.md %}) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
 **CockroachDB {{ site.data.products.basic }}**
Usage-based billing only		**CockroachDB {{ site.data.products.standard }}**
Provisioned compute, usage-based storage, data transfer, backups, and Change Data Capture (CDC)		**CockroachDB {{ site.data.products.advanced }}**
Provisioned compute, storage, and IOPS with usage-based billing for data transfer, backups, and CDC
[Compute](#compute)Usage-based via [Request Units]({% link cockroachcloud/create-a-basic-cluster.md %}#step-4-edit-cluster-capacity)Provisioned; cost per hour based on [vCPU quantity, cloud provider, and regions]({% link cockroachcloud/create-your-cluster.md %}#step-4-provision-cluster-capacity).Provisioned; cost per hour per node based on [vCPU quantity, cloud provider, and region]({% link cockroachcloud/create-an-advanced-cluster.md %}#step-5-configure-cluster-capacity)
IOPSUsage-based via Request UnitsFactored into storage costsProvisioned based on storage costs and varies per cloud provider
Data storageUsage-based + Usage-based, varies per cloud provider and regionProvisioned; billed per hour per node and varies per cloud provider and region
Managed backup storageDaily backups included in Request Unit costsUsage-based, varies per cloud provider and region.

Currently not charged during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics.md %}#backup-and-restore).		Usage-based, varies per cloud provider and region.

Currently not charged during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics.md %}#backup-and-restore).
[Data transfer](#data-transfer)Usage-based via Request UnitsUsage-based; cloud provider list price

Currently not charged during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics.md %}#backup-and-restore)		Usage-based; cloud provider list price

Currently not charged during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics.md %}#backup-and-restore)
[Change Data Capture]({% link {{site.current_cloud_version}}/change-data-capture-overview.md %})Usage-based via Request UnitsUsage-based.

Currently not charged during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics.md %}#backup-and-restore)		Usage-based.

Currently not charged during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics.md %}#backup-and-restore)
+ +To learn more about pricing in CockroachDB {{ site.data.products.cloud }}, refer to [Pricing](https://www.cockroachlabs.com/pricing/). + +## More details + +This section supplements the details in [Compare plans](#compare-plans). Select a plan to learn more. + +
+ + + +
+ +### Compute + +
+ +For CockroachDB {{ site.data.products.basic }}, compute is usage-based and calculated in Request Units. + +
+ +
+ +A CockroachDB {{ site.data.products.standard }} cluster's provisioned compute capacity is configured when the cluster is created and can be modified over time. This capacity represents the peak processing power the deployment can handle at any given time. + +Provisioned compute is calculated in vCPU-hours, with rates depending on the cloud provider and the region. Billing is based on the capacity reserved, not the actual usage. Charges are accumulated throughout the month to determine the total monthly compute charges. + +In a multi-region cluster, the price of the most expensive region is applied to the entire cluster’s compute capacity. The compute cost is calculated by multiplying the total provisioned capacity by the highest rate per vCPU-hour among all regions. + +Refer to [Pricing](https://www.cockroachlabs.com/pricing/). + +
+ +
+ +Each node of a CockroachDB {{ site.data.products.advanced }} cluster is provisioned with dedicated vCPU resources. You can [customize]({% link create-an-advanced-cluster.md %}#step-5-configure-cluster-capacity) the number of vCPUs per node. This configuration applies to all nodes in the cluster. Compute costs are based on the vCPUs provisioned for each node, at rates that vary rates depending on the cloud provider and region. + +Compute charges are calculated hourly by multiplying the hourly rate of the provisioned compute per node and number of nodes per cluster. These charges are accumulated throughout the month to determine the total monthly compute charges. When you configure your cluster's capacity, you are implicitly selecting a _machine type_ offered by the cloud provider. Different machine types are billed at different rates. The hourly compute cost is calculated by multiplying the hourly rate of the machine type by the number of nodes. + +Refer to [Pricing](https://www.cockroachlabs.com/pricing/). + +
+ +### Storage + +{{site.data.alerts.callout_info}} +There is no charge for backup storage during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics.md %}#backup-and-restore) +{{site.data.alerts.end}} + +
+ +Storage for CockroachDB {{ site.data.products.basic }} is automatically provisioned on demand, eliminating the need for manual management. Costs are based on actual usage and adjust dynamically as data is added or removed, starting from zero. + +Storage is billed hourly, with [rates](https://www.cockroachlabs.com/pricing) depending on the cloud provider and the region where the cluster is hosted.{% comment %}TODO: Resolve this contradiction. https://cockroachlabs.slack.com/archives/C05KHQULKFB/p1726955009576009{% endcomment %} + +
+ +
+ +Storage for CockroachDB {{ site.data.products.standard }} is automatically provisioned on demand, eliminating the need for manual management. Costs are based on actual usage and adjust dynamically as data is added or removed, starting from zero. + +A CockroachDB {{ site.data.products.standard }} cluster maintains a minimum of three replicas of your data, which are maintained at no additional cost. If you add further replicas, each will incur a storage cost equal to that of the logical database size. For more details, refer to [Plan a CockroachDB {{ site.data.products.standard }} cluster]({% link cockroachcloud/plan-your-cluster.md %}). + +Storage is billed hourly, with [rates](https://www.cockroachlabs.com/pricing) specific to each cloud provider and the region where the cluster is hosted. CockroachDB {{ site.data.products.cloud }} measures storage in GiB-hour. Hourly storage charges are accumulated throughout the month to determine the total monthly storage charges. + +
+ +
+ +Each CockroachDB {{ site.data.products.advanced }} cluster is provisioned with dedicated storage, configured when the cluster is created. The storage configuration applies to all nodes in the cluster. Storage is billed hourly, with [rates](https://www.cockroachlabs.com/pricing) depending on the cluster's cloud provider and regions. Storage costs are independent of compute costs, and you can adjust your cluster's storage capacity without altering its vCPU or memory configurations. Refer to [Plan a CockroachDB {{ site.data.products.advanced }} cluster]({% link cockroachcloud/plan-an-advanced-cluster.md %}). + +- **AWS**: For CockroachDB {{ site.data.products.advanced }} on AWS, storage charges are calculated per hour by multiplying the storage size in GiB by the hourly rate charged by AWS, plus any additional charges for IOPS. +- **GCP and Azure**: For CockroachDB {{ site.data.products.advanced }} on GCP or Azure, storage charges are calculated per hour by multiplying the storage size in GiB by the hourly rate charged by the cloud provider, with no additional fees for IOPS. + +Hourly storage charges are accumulated throughout the month to determine the total monthly storage charges. + +
+ +### Data transfer + +{{site.data.alerts.callout_info}} +There is no charge for data transfer during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics.md %}#backup-and-restore) +{{site.data.alerts.end}} + +
+For CockroachDB {{ site.data.products.basic }}, data transfer is included in the Request Unit price. +
+ +{% capture standard_and_advanced_data_transfer %} +The usage data is based on the volume of data transferred (per GiB), using the cloud provider's rate for the type of data transfer: to the same region, across regions, or across the public internet. +{% endcapture %} + +{% capture standard_and_advanced_cross_and_public %} +- **Cross-region**: When data is transferred from one region to another, this incurs additional cross-region charges, also known as inter-region charges. Data transfer across regions typically incurs higher costs than same-region transfer. +- **Public internet**: When data, manual backups, or logs are transferred or exported out of your cluster to SQL clients, third-party tools or storage, it is classified as public-internet data transfer. +{% endcapture %} + +Cloud providers may calculate each category differently. Refer to the documentation for the Cloud provider (AWS, GCP, or Azure). + +
+For CockroachDB {{ site.data.products.standard }}, data transfer is billed based on usage. + +{{ standard_and_advanced_data_transfer }} + +- **Same-region**: CockroachDB {{ site.data.products.standard }} stores data in three availability zones (AZs) per region. Data transfer among the AZs in the same region is classified as same-region data transfer. +{{ standard_and_advanced_cross_and_public }} + +
+ +
+For CockroachDB {{ site.data.products.advanced }}, data transfer is billed based on usage. + +{{ standard_and_advanced_data_transfer }} + +- **Same-region**: CockroachDB {{ site.data.products.advanced }} requires a minimum of three nodes per region, in three availability zones (AZs). Data transfer among the AZs in the same region is classified as same-region data transfer. +{{ standard_and_advanced_cross_and_public }} + +
+ +### Changefeeds + +All CockroachDB {{ site.data.products.cloud }} clusters can use [Enterprise Changefeeds](% link {{ site.current_cloud_version}}/how-does-an-enterprise-changefeed-work.md %). + +{{site.data.alerts.callout_info}} +There is no charge for changefeeds during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics.md %}#backup-and-restore) +{{site.data.alerts.end}} + +
+ +In CockroachDB {{ site.data.products.basic }}, Change Data Capture is included in the Request Unit price. +
+ +
+ +In CockroachDB {{ site.data.products.standard }}, Change Data Capture is billed monthly based on usage, and is calculated monthly based on the total GiB watched across all of a cluster's changefeeds, with the following thresholds: + +- < 5 GiB/month +- 5-100 GiB/month +- 100-250 GiB/month +- > 250 GiB/month + +
+ +
+ +In CockroachDB {{ site.data.products.standard }}, Change Data Capture is billed monthly based on usage, and is calculated monthly based on the total GiB watched across all of a cluster's changefeeds, with the following thresholds: + +- < 5 GiB/month +- 5-100 GiB/month +- 100-250 GiB/month +- > 250 GiB/month + +
+ +## Next steps + +- [Plan a CockroachDB {{ site.data.products.basic }} cluster]({% link cockroachcloud/plan-your-cluster-basic.md %}) and [Create a CockroachDB {{ site.data.products.basic }} cluster]({% link cockroachcloud/create-a-basic-cluster.md %}). +- [Plan a CockroachDB {{ site.data.products.standard }} cluster]({% link cockroachcloud/plan-your-cluster.md %}) and [Create a CockroachDB {{ site.data.products.standard }} cluster]({% link create-your-cluster.md %}) +- [Plan a CockroachDB {{ site.data.products.advanced }} cluster]({% link cockroachcloud/plan-your-cluster-advanced.md %}) and [Create a CockroachDB {{ site.data.products.advanced }} cluster]{% link cockroachcloud/create-an-advanced-cluster.md %} + +{% comment %}Old content below

CockroachDB Cloud Docs

@@ -150,3 +383,4 @@ docs_area:
+{% endcomment %} diff --git a/src/current/cockroachcloud/plan-your-cluster.md b/src/current/cockroachcloud/plan-your-cluster.md index 66a34b13c16..4340ebf2fb4 100644 --- a/src/current/cockroachcloud/plan-your-cluster.md +++ b/src/current/cockroachcloud/plan-your-cluster.md @@ -1,5 +1,5 @@ --- -title: Plan a CockroachDB {{ site.data.products.standard }} Cluster [WIP] +title: Plan a CockroachDB Standard Cluster summary: Plan your cluster's configuration. toc: true docs_area: deploy @@ -8,163 +8,99 @@ cloud: true {% include cockroachcloud/filter-tabs/plan-your-cluster.md %} -This page describes how resource usage, pricing, and cluster configurations work in CockroachDB {{ site.data.products.standard }}. For information on diagnosing and optimizing your resource consumption, see [Optimize your Resource Usage]({% link cockroachcloud/resource-usage.md %}). +This page provides guidance for planning and estimating costs for a CockroachDB {{ site.data.products.standard }} cluster that meets your business requirements. For information on diagnosing and optimizing your resource consumption, see [Optimize your Resource Usage]({% link cockroachcloud/resource-usage.md %}). -# Capacity (Compute) resources +## Provisioned capacity -The *compute* resources available to Standard clusters are provisioned and scaled using a *provisioned capacity* model based on *vCPUs* as the unit of measurement. The amount of capacity required for a Standard cluster is entirely dependent on the scale and query profile of the workload, and may change over time as the workload evolves. Note that *storage capacity* in Standard is allocated as needed for the current data volume, so it is not covered here under capacity provisioning. See section [Estimating storage pricing for Standard clusters below](\#estimating-storage-pricing-for-standard-clusters). +The compute resources available to a CockroachDB {{ site.data.products.standard }} cluster is provisioned and scaled using a capacity model measured in _virtual CPUs (vCPUs)_. A cluster's capacity requirements depend on the scale and query profile of the cluster's workload, and may change over time as the workload evolves. It’s typical to estimate the initial compute capacity needed for a workload before creating the cluster, and to adjust the capacity up or down based observation of the workload's consumption. -It’s typical to roughly estimate the compute capacity needed for a workload before creating the Standard cluster and then easily adjust that capacity up or down based on observing the actual compute capacity consumed by the workload. +Storage for a CockroachDB {{ site.data.products.standard }} cluster is allocated on demand and is not covered in this section. Refer to [Storage](#storage-pricing) -## Quick start: Provisioning and adjusting capacity - +### Quickstart: Provision and adjust capacity -Use this section as the easiest way to arrive at the right capacity for your CockroachDB {{ site.data.products.standard }} deployment. Because each workload is different, it is difficult to estimate the required capacity up front. So we recommend starting with a rough estimate and then using the easy scaling capability of Standard to adjust capacity based on workload performance as it evolves. +To achieve a rough initial estimate of compute capacity, consider: -### Step 1: Estimating initial cluster compute capacity +- **Expected workload maximum**: the maximum expected long-term compute consumption for the workload, measured in vCPUs. + - If your workload is already using CockroachDB {{ site.data.products.core }} and is performing well, we recommend that you start with the sum of the compute capacity of its nodes across all regions. + - If you are moving the workload from another database and is performing well, we recommend that you consider its historical compute requirements to arrive at an initial compute capacity. + - [Talk to an expert](https://www.cockroachlabs.com/contact/). Engineers at Cockroach Labs will work with you to understand the resource demands of your workload and help you estimate and validate its required capacity. -Follow these steps to achieve a rough initial estimate of compute capacity provisioning for CockroachDB {{ site.data.products.standard }}: +- **Additional capacity buffer**: To accommodate unanticipated load and mitigate the risk of application degradation if the cluster's capacity is exceeded, we recommend that you plan for additional capacity beyond your initial estimate. A 40% buffer is a good starting point, but more may be needed if the workload is unpredictable or highly sensitive to query latency. Depending on the nature of the workload, such as when demand is seasonal, you can plan to scale the cluster's capacity temporarily to address the workload's requirements. + - **Exceeding capacity limit**: CockroachDB {{ site.data.products.standard }} enforces the cluster's provisioned capacity, limiting application throughput if the workload exceeds the cluster's provisioned capacity. This can lead to increased query latency and degraded application performance. + - **Notifications to prevent overrun**: To help mitigate against the risk of exceeding a cluster's capacity, email and CockroachDB {{ site.data.products.cloud }} Console notifications will occur when a cluster workload exceeds 90% and 90% of its provisioned capacity. -1. **Expected workload maximum** \- Estimate the maximum expected long-term workload compute consumption as measured by the number of vCPUs consumed: - 1. If your workload is already running on another form of CockroachDB, use the current total number of vCPUs (across all nodes and regions) as the initial configured value for the number of vCPUs in your Standard cluster. - 2. If the workload has previously run on another DBMS, extrapolate from its historical vCPU consumption - 3. [Talk to an expert](https://www.cockroachlabs.com/contact/).. Our engineers will work with you to understand the resource demands of your specific workload and help you estimate required capacity. +- **Multi-region deployments**: The provisioned capacity of your cluster applies to the entire cluster, regardless of the number of nodes or regional topography. The provisioned capacity is effectively a budget for the cluster that can be used by a node in any region to meet its compute demand. This simplifies planning compute capacity for multi-region deployments. The overall [compute capacity cost]({% link cockroachcloud/billing.md %}) for a multi-region CockroachDB {{ site.data.products.standard }} cluster is calculated based on the price of the most expensive region in the cluster. -2. **Additional capacity buffer** \- Add additional capacity as a buffer to accommodate unanticipated load and mitigate risk of application degradation if provisioned capacity is exceeded. We recommend 40% buffer capacity on top of the expected workload max. +After considering the above factors, you have enough information to [create a CockroachDB {{ site.data.products.standard }} cluster]({% link cockroachcloud/create-your-cluster.md %}) using the CockroachDB {{ site.data.products.cloud }} Console or the [CockroachDB Terraform provider]({% link cockroachcloud/provision-a-cluster-using-terraform.md %}). After the cluster is deployed, you can [scale its compute capacity]({% link cockroachcloud/cluster-management.md %}#edit-cluster-capacity) by increasing or decreasing its provisioned capacity as needed. -3. **For multi-region deployments** \- The provisioned capacity of your Standard cluster applies to the entire cluster regardless of the number of regions or regional topography. The provisioned capacity acts as an overall budget that can be drawn from by any region depending on its current compute demand, making it easier to operate multi-region deployments in CockroachDB {{ site.data.products.standard }}. +{{site.data.alerts.callout_success}} +You can decrease the provisioned capacity only three times within a 7-day period. You can increase the provisioned capacity at any time. +{{site.data.alerts.end}} -4. **Configure initial capacity and create the cluster** \- Once the initial estimate has been determined, configure the cluster's initial provisioned capacity during cluster creation via the [Console UI](http://cockroachlabs.cloud) or via the [CockroachDB Terraform provider](https://registry.terraform.io/providers/cockroachdb/cockroach/latest). +The CockroachDB {{ site.data.products.cloud }} Console provides insight into your cluster's compute usage relative to its provisioned capacity on a monthly basis. We recommend that you maintain at minimum a 40% capacity buffer over time, and that you increase this buffer if the workload is unpredictable or highly sensitive to query latency. You now have the advantage of historical data about the cluster's performance to help you maintain and improve the cluster's performance over time. -### Step 2: Altering provisioned capacity for existing clusters by scaling up or down +### Capacity pricing policies -\ +Important capacity and pricing policies mentioned elsewhere are summarized here: -## Comprehensive guide: Understanding CockroachDB {{ site.data.products.standard }} capacity +- **Minimum and maximum provisioned capacity**: - A CockroachDB {{ site.data.products.standard }} cluster must have a provisioned capacity of at minimum 2 vCPUs. For production workloads, we recommend at minimum 4 to 8 vCPUs. The maximum capacity for CockroachDB {{ site.data.products.standard }} is 60 vCPUs. To express interest in higher-capacity clusters, [talk to an expert](https://www.cockroachlabs.com/contact/). -We recommend using Quick start: Provisioning and adjusting capacity as the most straightforward and accurate way to arrive at the best initial Standard cluster capacity for your workload and maintain the right capacity as the workload evolves. +- **Enforcing provisioned capacity limits**: CockroachDB {{ site.data.products.cloud }} enforces the cluster’s provisioned capacity, limiting application throughput if the workload exceeds the capacity limit. This can result in degraded performance and increased query latency. You can increase a cluster's capacity at any time. -The Quick start approach involves using a rough estimate initially, observing actual performance, and then making adjustments to refine the original estimate. If you want to pursue a more rigorous initial estimate in the context of evaluating whether Standard or Advanced is the right fit for your workload, the following sections are designed to help you. +- **Capacity for multi-region clusters**: A multi-region cluster's capacity is available to all cluster nodes in all regions, but is not pre-allocated per region. The cluster's CPU utilization across regions cannot exceed its provisioned capacity. -### Standard and Advanced have equivalent performance *on average* but not for every workload +- **Multi-region pricing by the most expensive region**: The overall [compute capacity cost]({% link cockroachcloud/billing.md %}) for a multi-region CockroachDB {{ site.data.products.standard }} cluster is calculated based on the price of the most expensive region in the cluster. -Standard and Advanced are designed to be as interchangeable as possible in terms of compute capacity and operational features. See the [feature comparison table](http://cockroachlabs.com/pricing) for detailed explanation of feature differences between the two products. While consistency across the two products is the goal, the two are based on different computational platforms and may differ considerably in terms of their compute requirements *depending on the workload*. +- **Limitations on capacity scaling**: You can decrease the provisioned capacity only three times within a 7-day period. You can increase the provisioned capacity at any time. -* **Equivalence *on average*** \- Standard vCPUs and Advanced vCPUs have equivalent compute performance averaged across all workloads -* **Highly variable with workload** \- while equivalent on average, the vCPU performance comparison between Standard and Advanced varies significantly with the workload. There are two factors driving this variance: - * *Workloads are unpredictable* \- OLTP workloads are remarkably diverse in their resources utilization across industries and applications - * *Architectural differences* \- Standard and Advanced are built on different underlying CockroachDB deployment architectures that have different performance characteristics +### More details about capacity -### Standard vCPUs are priced at 60% of Advanced vCPUs +We recommend that you start with [Quickstart: Provisioning and adjusting capacity](#quickstart-provision-and-adjusting-capacity) to arrive at the best initial compute capacity for your workload and that you adjust the cluster's capacity over time as the workload evolves. In addition, consider the following: -The pricing per-vCPUs does not depend in any way on the workload. Standard vCPUs are priced at 60% of the price of Advanced vCPUs, with some slight variations depending on the cloud provider and region. Since vCPUs are equivalent between Standard and Advanced on average, both plans require the same number of vCPUs on average, so total cluster cost for Standard is 60% of Advanced *on average*. +- **Smaller workloads**: CockroachDB {{ site.data.products.standard }} is well suited for workloads that require 12 or fewer vCPUs. By contrast, 12 vCPUs (3 nodes x 4 vCPUs) is the minimum configuration for CockroachDB {{ site.data.products.advanced }}. -But workloads may vary significantly from the average, so the estimation challenge is one of predicting the actual number of vCPUs a workload may require, regardless of whether you’re considering Standard or Advanced. + CockroachDB {{ site.data.products.standard }} is not recommended for: + - Analytical workloads that involve a large quantity of large, complex reads + - OLAP or hybrid OLTP/OLAP applications -### Comparing total cluster vCPU capacity cost between Standard and Advanced +- **Asymmetric multi-region workloads**: Often, multi-region deployments are asymmetric in terms of CPU utilization across regions. For example, in a three-region cluster, two of the three regions may require more capacity than the third, or vice versa. In CockroachDB {{ site.data.products.standard }}, a cluster's compute capacity is available in all regions. -Given that Standard vCPUs are priced at 60% of Advanced vCPUs, estimating the cost of a workload on Standard as compared to Advanced means estimating the difference in number of vCPUs required between the two plans. For some workloads, Standard requires higher vCPU capacity, for others Advanced, depending on the properties of the workload and how the different underlying CockroachDB deployment architectures provide resources to that workload. + For workloads that require symmetric capacity per region or where a given region must maintain a given compute capacity, CockroachDB {{ site.data.products.advanced }} may be a better option. -### vCPU capacity ranges based on Cockroach Labs testing +- **Workloads that are sensitive to latency**: CockroachDB {{ site.data.products.standard }} clusters use a different networking architecture than CockroachDB {{ site.data.products.advanced }}. This architecture can introduce additional query latency of around 1 microsecond when compared with CockroachDB {{ site.data.products.advanced }}. -In our internal testing, running a wide range of workloads on both Standard and Advanced, we’ve seen the following results: +- **Workloads with advanced security or compliance requirements**: For workloads subject to advanced security or compliance requirements, consider CockroachDB {{ site.data.products.advanced }}, which complies with [PCI DSS and HIPAA]({% link cockroachcloud/pci-dss.md %}). To learn more refer to [Compliance in CockroachDB {{ site.data.products.cloud }}]({% link cockroachcloud/compliance.md %}). -Outcome: For 75% of all all tested workloads, the required Standard total cluster cost (in $ per month) is within 40% \- 70% of the total Advanced cluster cost (in $ per month). +For more details to help you compare CockroachDB {{ site.data.products.cloud }} cluster plans, refer to [TBD COMPARISON PAGE](/). -The following histogram provides more detail on the test outcomes. -![][image3] +## Storage pricing -## Examples and Benchmarks for vCPU Capacity +Storage capacity for a CockroachDB {{ site.data.products.standard }} cluster is [priced]({% link cockroachcloud/billing.md %}) on demand in units of GiB-month. Storage prices vary across providers and [regions]({% link cockroachcloud/regions.md %}). Storage is charged based on the logical amount of data in the database. +- **3 replicas included**: - CockroachDB {{ site.data.products.standard }} maintains at minimum three replicas of your data at no additional cost. -Comparing relative CPU utilization for several benchmarks. Understanding the results below: + For a cluster with more than three replicas, storage for each additional replica is priced at the storage price for the region. -### TPC-C +- **Multi-region storage**: In a multi-region cluster, storage prices vary by region. The data in each region is priced at that region's storage rate. -[TPC](https://www.tpc.org/tpcc/) is an industry standard performance benchmark for OLTP workloads. +### Single-region example -| | Standard vCPUs | Advanced vCPUs | vCPU ratio | Standard vCPU cost | Advanced vCPU cost | Standard price-perf savings | -| :---- | :---- | :---- | :---- | :---- | :---- | :---- | -| TPC-C (150 warehouses) | 4.98 | 4.86 | 1.03 | $378 | $615 | 39% | -| TPC-C (300 warehouses) | 6.51 | 6.51 | 1.00 | $495 | $825 | 40% | -| | | | | | | | +By default, CockroachDB {{ site.data.products.cloud }} maintains three replicas for a single-region cluster, spread across three different availability zones within the region. You are not charged to store these replicas. +For example, if a single-region cluster is deployed in `us-central-1` and contains 500 GiB of data. CockroachDB {{ site.data.products.cloud }} stores three replicas, for a total of 1500 GiB of data. However, you are billed only for 500 GiB of storage. -TODO - remove original table +If you add a fourth replicas, the cluster consumes 2000 GiB of storage (500 x 4), but you are billed only for 1000 GiB (500 for the data and 500 for the fourth replica). -| TPC-C (150 warehouses) | 4.86 | 4.98 | $61.54 | -| :---- | ----: | ----: | ----: | -| TPC-C (300 warehouses) | 6.51 | 6.51 | $60.04 | -| TPC-C (600 warehouses) | 9.45 | 10.90 | $69.21 | -| TPC-E (500 customers) | 4.20 | 3.85 | $54.97 | -| TPC-H (query \#1) | 10.64 | 18.81 | $106.03 | -| TPC-H (query \#2) | 10.41 | 10.42 | $60.07 | -| TPC-H (query \#11) | 11.02 | 12.83 | $69.87 | -| TPC-H (query \#13) | 5.23 | 4.43 | $50.81 | +### Multi-region example -This table is \[WIP\] +For multi-region clusters, we recommend 5 or more replicas are typically maintained across availability zones and regions for resilience against both zone and region failure. The first three replicas are included in the base storage price, while additional replicas are priced based on the ratio of additional regions to the initial three. -| | Advanced vCPU | Standard CPU | Standard Price | -| :---- | ----- | ----- | ----- | -| KV write-only (100 QPS) | 1.26 | 0.71 | $34.00 | -| KV write-only (200 QPS) | 1.68 | 1.13 | $40.37 | -| KV write-only (400 QPS) | 2.34 | 1.94 | $49.80 | -| KV write-only (800 QPS) | 3.35 | 3.12 | $55.95 | -| KV write-only (1600 QPS) | 4.79 | 4.67 | $58.48 | -| KV write-only (3200 QPS) | 6.86 | 7.50 | $65.56 | -| KV write-only (6400 QPS) | 9.49 | 12.05 | $76.20 | -| KV write-only (1 byte payload) | 6.89 | 7.80 | $67.96 | -| KV write-only (256 byte payload) | 6.96 | 7.90 | $68.08 | -| KV write-only (1K payload) | 7.11 | 8.77 | $74.01 | -| KV write-only (4K payload) | 5.80 | 6.53 | $67.58 | -| KV write-only (16K payload) | 6.03 | 5.96 | $59.26 | -| KV write-only (64K payload) | 6.30 | 6.81 | $64.84 | -| KV write-only (256K payload) | 7.46 | 6.74 | $54.22 | -| KV write-only (3 requests / batch) | 2.27 | 1.96 | $52.02 | -| KV write-only (6 requests / batch) | 2.36 | 2.27 | $57.85 | -| KV write-only (11 requests / batch) | 2.60 | 2.50 | $57.60 | -| KV write-only (22 requests / batch) | 2.82 | 2.95 | $62.87 | -| KV write-only (43 requests / batch) | 3.62 | 3.90 | $64.65 | -| KV write-only (84 requests / batch) | 5.47 | 5.03 | $55.15 | -| KV write-only (400 QPS, secondary index) | 3.84 | 3.85 | $60.17 | -| KV write-only (800 QPS, secondary index) | 5.71 | 5.97 | $62.81 | -| KV write-only (1600 QPS, secondary index) | 9.12 | 9.65 | $63.48 | -| KV write-only (3200 QPS, secondary index) | 14.82 | 16.20 | $65.58 | -| KV read-only (800 QPS) | 1.62 | 1.08 | $39.90 | -| KV read-only (1600 QPS) | 2.36 | 2.01 | $51.26 | -| KV read-only (3200 QPS) | 3.56 | 3.56 | $60.14 | -| KV read-only (6400 QPS) | 5.68 | 6.64 | $70.20 | -| KV read-only (1 byte payload) | 3.62 | 3.73 | $61.73 | -| KV read-only (256 byte payload) | 3.46 | 4.03 | $69.98 | -| KV read-only (1K payload) | 3.67 | 4.44 | $72.50 | -| KV read-only (4K payload) | 2.55 | 2.88 | $67.68 | -| KV read-only (16K payload) | 2.85 | 3.30 | $69.63 | -| KV read-only (64K payload) | 4.07 | 4.40 | $64.95 | -| KV read-only (256K payload) | 4.28 | 4.42 | $62.04 | -| KV read-only (8 requests / batch) | 2.18 | 1.78 | $48.90 | -| KV read-only (16 requests / batch) | 2.28 | 2.11 | $55.45 | -| KV read-only (32 requests / batch) | 2.64 | 2.62 | $59.48 | -| KV read-only (64 requests / batch) | 3.41 | 3.52 | $61.92 | -| TPC-C (150 warehouses) | 4.86 | 4.98 | $61.54 | -| TPC-C (300 warehouses) | 6.51 | 6.51 | $60.04 | -| TPC-C (600 warehouses) | 9.45 | 10.90 | $69.21 | -| TPC-E (500 customers) | 4.20 | 3.85 | $54.97 | -| TPC-H (query \#1) | 10.64 | 18.81 | $106.03 | -| TPC-H (query \#2) | 10.41 | 10.42 | $60.07 | -| TPC-H (query \#11) | 11.02 | 12.83 | $69.87 | -| TPC-H (query \#13) | 5.23 | 4.43 | $50.81 | -| MOVR | 3.1 | 2.92 | $55.99 | -| Bank | 4.9 | 4.67 | $57.03 | -| Ledger | 1.8 | 1.80 | $58.57 | -| YCSB (query A) | 4.8 | 5.34 | $67.28 | -| YCSB (query B) | 2.8 | 3.74 | $81.21 | -| YCSB (query C) | 2.4 | 3.28 | $80.75 | -| YCSB (query D) | 2.7 | 4.02 | $88.91 | -| YCSB (query E) | 5.8 | 6.19 | $64.14 | -| YCSB (query F) | 5.1 | 5.77 | $68.23 | -| Import (TPC-C 500 warehouses) | 20.7 | 19.00 | $55.05 | -| Import (TPC-H 3GB) | 11.8 | 6.81 | $34.65 | - -# Estimating storage pricing for Standard clusters - -WIP +Consider the example of a three-region cluster with 500 GiB of logical data, deployed in `us-central1`, `us-west2`, and `europe-west1`, with 5 replicas. The logical data and the first three replicas are included in the monthly storage cost. The additional two replicas are charged at 2/3 of the monthly storage cost. This cluster consumes 2500 GiB of storage, but is billed for 1500 GiB for the initial data and 3 replicas, plus 2/3 of the additional 1000 GiB for the additional two replicas (2 replicas beyond the initial 3). +If you add a 6th replica, the cluster will consume 3000 GiB (500 x 6), and will be billed for 1500 GiB for the initial data and 3 replicas, plus 100% (3/3) of the additional three replicas (3 replicas beyond the initial 3). + +## See also + +- [Create a CockroachDB {{ site.data.products.standard }} cluster]({% link cockroachcloud/create-your-cluster.md %}) +- [Edit cluster capacity]({% link cockroachcloud/cluster-management.md %}#edit-cluster-capacity) +- [Plan an CockroachDB {{ site.data.products.advanced }} cluster]({% link cockroachcloud/plan-an-advanced-cluster.md %}) +- [Plan an CockroachDB {{ site.data.products.basic }} cluster]({% link cockroachcloud/plan-a-basic-cluster.md %}) From 894c4485d94cf3f611485fdcbf2bb6308ab60f14 Mon Sep 17 00:00:00 2001 From: Matt Linville Date: Sat, 21 Sep 2024 15:22:53 -0700 Subject: [PATCH 02/16] Fix link --- src/current/cockroachcloud/cluster-management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/current/cockroachcloud/cluster-management.md b/src/current/cockroachcloud/cluster-management.md index 30f75ec77fd..6b53369739c 100644 --- a/src/current/cockroachcloud/cluster-management.md +++ b/src/current/cockroachcloud/cluster-management.md @@ -53,7 +53,7 @@ To edit your cluster's capacity: 1. In the sidebar, verify the new estimated cost for the cluster and click **Update cluster**. -To learn more, refer to [Plan a CockroachDB {{ site.data.products.standard }} cluster]({% link plan-your-cluster.md %}#provisioned-capacity). +To learn more, refer to [Plan a CockroachDB {{ site.data.products.standard }} cluster]({% link cockroachcloud/plan-your-cluster.md %}#provisioned-capacity). ## Manage cluster upgrades From 67da6450d90389b4ba7e393b11595be798716cf0 Mon Sep 17 00:00:00 2001 From: Matt Linville Date: Sat, 21 Sep 2024 15:28:52 -0700 Subject: [PATCH 03/16] Fix links, try to fix Cloud landing page width --- src/current/cockroachcloud/index.md | 158 ++-------------------------- 1 file changed, 6 insertions(+), 152 deletions(-) diff --git a/src/current/cockroachcloud/index.md b/src/current/cockroachcloud/index.md index 0ddc0afc858..f4dc9a4808c 100644 --- a/src/current/cockroachcloud/index.md +++ b/src/current/cockroachcloud/index.md @@ -1,11 +1,10 @@ --- title: CockroachDB Cloud docs summary: Learn more about CockroachDB Cloud, a fully-managed service created and owned by Cockroach Labs that makes deploying, scaling, and managing CockroachDB effortless. -toc: true -contribute: true +toc: false +contribute: false cta: false -homepage: true -docs_area: +homepage: false --- ## Overview @@ -28,9 +27,9 @@ When you create a cluster in CockroachDB {{ site.data.products.cloud }}, you sel This section summarizes key details about each plan to help you make the best choice for each cluster and its workload. For more details, refer to: -- [Plan a CockroachDB {{ site.data.products.basic }} cluster]({% link cockroachcloud/plan-a-basic-cluster.md %}) +- [Plan a CockroachDB {{ site.data.products.basic }} cluster]({% link cockroachcloud/plan-your-cluster-basic.md %}) - [Plan a CockroachDB {{ site.data.products.standard }} cluster]({% link cockroachcloud/plan-your-cluster.md %}) -- [Plan a CockroachDB {{ site.data.products.advanced }} cluster]({% link cockroachcloud/plan-an-advanced-cluster.md %}) +- [Plan a CockroachDB {{ site.data.products.advanced }} cluster]({% link cockroachcloud/plan-your-cluster-advanced.md %}) @@ -149,7 +148,7 @@ Storage is billed hourly, with [rates](https://www.cockroachlabs.com/pricing) sp
-Each CockroachDB {{ site.data.products.advanced }} cluster is provisioned with dedicated storage, configured when the cluster is created. The storage configuration applies to all nodes in the cluster. Storage is billed hourly, with [rates](https://www.cockroachlabs.com/pricing) depending on the cluster's cloud provider and regions. Storage costs are independent of compute costs, and you can adjust your cluster's storage capacity without altering its vCPU or memory configurations. Refer to [Plan a CockroachDB {{ site.data.products.advanced }} cluster]({% link cockroachcloud/plan-an-advanced-cluster.md %}). +Each CockroachDB {{ site.data.products.advanced }} cluster is provisioned with dedicated storage, configured when the cluster is created. The storage configuration applies to all nodes in the cluster. Storage is billed hourly, with [rates](https://www.cockroachlabs.com/pricing) depending on the cluster's cloud provider and regions. Storage costs are independent of compute costs, and you can adjust your cluster's storage capacity without altering its vCPU or memory configurations. Refer to [Plan a CockroachDB {{ site.data.products.advanced }} cluster]({% link cockroachcloud/plan-your-cluster-advanced.md %}). - **AWS**: For CockroachDB {{ site.data.products.advanced }} on AWS, storage charges are calculated per hour by multiplying the storage size in GiB by the hourly rate charged by AWS, plus any additional charges for IOPS. - **GCP and Azure**: For CockroachDB {{ site.data.products.advanced }} on GCP or Azure, storage charges are calculated per hour by multiplying the storage size in GiB by the hourly rate charged by the cloud provider, with no additional fees for IOPS. @@ -239,148 +238,3 @@ In CockroachDB {{ site.data.products.standard }}, Change Data Capture is billed - [Plan a CockroachDB {{ site.data.products.basic }} cluster]({% link cockroachcloud/plan-your-cluster-basic.md %}) and [Create a CockroachDB {{ site.data.products.basic }} cluster]({% link cockroachcloud/create-a-basic-cluster.md %}). - [Plan a CockroachDB {{ site.data.products.standard }} cluster]({% link cockroachcloud/plan-your-cluster.md %}) and [Create a CockroachDB {{ site.data.products.standard }} cluster]({% link create-your-cluster.md %}) - [Plan a CockroachDB {{ site.data.products.advanced }} cluster]({% link cockroachcloud/plan-your-cluster-advanced.md %}) and [Create a CockroachDB {{ site.data.products.advanced }} cluster]{% link cockroachcloud/create-an-advanced-cluster.md %} - -{% comment %}Old content below -
-
-

CockroachDB Cloud Docs

-

Get your applications to market faster with a fully managed CockroachDB instance.

-
-
-
- -
-
Quickstart with
CockroachDB Cloud
-

Learn how to create and use your CockroachDB {{ site.data.products.cloud }} cluster

-

Learn more arrow right

-
- -
-
-
-
- -
-
Manage your
cluster
-

Manage your cluster's schema, data, and backups

-

Learn more arrow right

-
- -
-
-
-
-
-
-
- Start a Free Serverless Cluster arrow left -
-
- -
- -
-
-

CockroachDB Cloud

-

Recommended articles

-
-
- -
-
-

Get Started

-
- -
-
-
-

Use Your Cluster

-
- -
-
-
-

Develop

-
- -
-
-
-

Learn More

-
- -
-
-
- -
-
-
- - - - -
-
-
- -
-
-
-
-

- CockroachDB Cloud -

-
- Connecting to Your CockroachDB Cloud Cluster -
-
-
-
-
-
-
- -
-{% endcomment %} From 34fe1e990717953e4491a07f51782c2e0b26f621 Mon Sep 17 00:00:00 2001 From: Matt Linville Date: Sat, 21 Sep 2024 18:08:46 -0700 Subject: [PATCH 04/16] More link fixes --- src/current/cockroachcloud/index.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/src/current/cockroachcloud/index.md b/src/current/cockroachcloud/index.md index f4dc9a4808c..fdf61483ea6 100644 --- a/src/current/cockroachcloud/index.md +++ b/src/current/cockroachcloud/index.md @@ -114,7 +114,7 @@ Refer to [Pricing](https://www.cockroachlabs.com/pricing/).
-Each node of a CockroachDB {{ site.data.products.advanced }} cluster is provisioned with dedicated vCPU resources. You can [customize]({% link create-an-advanced-cluster.md %}#step-5-configure-cluster-capacity) the number of vCPUs per node. This configuration applies to all nodes in the cluster. Compute costs are based on the vCPUs provisioned for each node, at rates that vary rates depending on the cloud provider and region. +Each node of a CockroachDB {{ site.data.products.advanced }} cluster is provisioned with dedicated vCPU resources. You can [customize]({% link cockroachcloud/create-an-advanced-cluster.md %}#step-5-configure-cluster-capacity) the number of vCPUs per node. This configuration applies to all nodes in the cluster. Compute costs are based on the vCPUs provisioned for each node, at rates that vary rates depending on the cloud provider and region. Compute charges are calculated hourly by multiplying the hourly rate of the provisioned compute per node and number of nodes per cluster. These charges are accumulated throughout the month to determine the total monthly compute charges. When you configure your cluster's capacity, you are implicitly selecting a _machine type_ offered by the cloud provider. Different machine types are billed at different rates. The hourly compute cost is calculated by multiplying the hourly rate of the machine type by the number of nodes. @@ -233,8 +233,14 @@ In CockroachDB {{ site.data.products.standard }}, Change Data Capture is billed
+## Usage-based metrics in Preview + +Usage-based metrics for [data transfer](#data-transfer), [managed backup storage](#storage), and [Change Data Capture](#change-data-capture) are in [Preview]({% link {{site.current_cloud_version }}/cockroachdb-feature-availability.md %}#features-in-preview). You can view the usage of these metrics in your invoice page under **Billing**. + +There will be no additional charges for these metrics during the preview period, which is in effect until December, 2024. During this time, charges will appear as $0 on your monthly invoice. + ## Next steps - [Plan a CockroachDB {{ site.data.products.basic }} cluster]({% link cockroachcloud/plan-your-cluster-basic.md %}) and [Create a CockroachDB {{ site.data.products.basic }} cluster]({% link cockroachcloud/create-a-basic-cluster.md %}). -- [Plan a CockroachDB {{ site.data.products.standard }} cluster]({% link cockroachcloud/plan-your-cluster.md %}) and [Create a CockroachDB {{ site.data.products.standard }} cluster]({% link create-your-cluster.md %}) +- [Plan a CockroachDB {{ site.data.products.standard }} cluster]({% link cockroachcloud/plan-your-cluster.md %}) and [Create a CockroachDB {{ site.data.products.standard }} cluster]({% link cockroachcloud/create-your-cluster.md %}) - [Plan a CockroachDB {{ site.data.products.advanced }} cluster]({% link cockroachcloud/plan-your-cluster-advanced.md %}) and [Create a CockroachDB {{ site.data.products.advanced }} cluster]{% link cockroachcloud/create-an-advanced-cluster.md %} From 6255ef672a4ba884ca3ae686cea8ca40eb974670 Mon Sep 17 00:00:00 2001 From: Matt Linville Date: Mon, 23 Sep 2024 15:18:32 -0700 Subject: [PATCH 05/16] Fix links to billing --- src/current/cockroachcloud/plan-your-cluster.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/current/cockroachcloud/plan-your-cluster.md b/src/current/cockroachcloud/plan-your-cluster.md index 4340ebf2fb4..02ba48a5260 100644 --- a/src/current/cockroachcloud/plan-your-cluster.md +++ b/src/current/cockroachcloud/plan-your-cluster.md @@ -29,7 +29,7 @@ To achieve a rough initial estimate of compute capacity, consider: - **Exceeding capacity limit**: CockroachDB {{ site.data.products.standard }} enforces the cluster's provisioned capacity, limiting application throughput if the workload exceeds the cluster's provisioned capacity. This can lead to increased query latency and degraded application performance. - **Notifications to prevent overrun**: To help mitigate against the risk of exceeding a cluster's capacity, email and CockroachDB {{ site.data.products.cloud }} Console notifications will occur when a cluster workload exceeds 90% and 90% of its provisioned capacity. -- **Multi-region deployments**: The provisioned capacity of your cluster applies to the entire cluster, regardless of the number of nodes or regional topography. The provisioned capacity is effectively a budget for the cluster that can be used by a node in any region to meet its compute demand. This simplifies planning compute capacity for multi-region deployments. The overall [compute capacity cost]({% link cockroachcloud/billing.md %}) for a multi-region CockroachDB {{ site.data.products.standard }} cluster is calculated based on the price of the most expensive region in the cluster. +- **Multi-region deployments**: The provisioned capacity of your cluster applies to the entire cluster, regardless of the number of nodes or regional topography. The provisioned capacity is effectively a budget for the cluster that can be used by a node in any region to meet its compute demand. This simplifies planning compute capacity for multi-region deployments. The overall [compute capacity cost]({% link cockroachcloud/billing-management.md %}) for a multi-region CockroachDB {{ site.data.products.standard }} cluster is calculated based on the price of the most expensive region in the cluster. After considering the above factors, you have enough information to [create a CockroachDB {{ site.data.products.standard }} cluster]({% link cockroachcloud/create-your-cluster.md %}) using the CockroachDB {{ site.data.products.cloud }} Console or the [CockroachDB Terraform provider]({% link cockroachcloud/provision-a-cluster-using-terraform.md %}). After the cluster is deployed, you can [scale its compute capacity]({% link cockroachcloud/cluster-management.md %}#edit-cluster-capacity) by increasing or decreasing its provisioned capacity as needed. @@ -49,7 +49,7 @@ Important capacity and pricing policies mentioned elsewhere are summarized here: - **Capacity for multi-region clusters**: A multi-region cluster's capacity is available to all cluster nodes in all regions, but is not pre-allocated per region. The cluster's CPU utilization across regions cannot exceed its provisioned capacity. -- **Multi-region pricing by the most expensive region**: The overall [compute capacity cost]({% link cockroachcloud/billing.md %}) for a multi-region CockroachDB {{ site.data.products.standard }} cluster is calculated based on the price of the most expensive region in the cluster. +- **Multi-region pricing by the most expensive region**: The overall [compute capacity cost]({% link cockroachcloud/billing-management.md %}) for a multi-region CockroachDB {{ site.data.products.standard }} cluster is calculated based on the price of the most expensive region in the cluster. - **Limitations on capacity scaling**: You can decrease the provisioned capacity only three times within a 7-day period. You can increase the provisioned capacity at any time. @@ -75,7 +75,7 @@ For more details to help you compare CockroachDB {{ site.data.products.cloud }} ## Storage pricing -Storage capacity for a CockroachDB {{ site.data.products.standard }} cluster is [priced]({% link cockroachcloud/billing.md %}) on demand in units of GiB-month. Storage prices vary across providers and [regions]({% link cockroachcloud/regions.md %}). Storage is charged based on the logical amount of data in the database. +Storage capacity for a CockroachDB {{ site.data.products.standard }} cluster is [priced]({% link cockroachcloud/billing-management.md %}) on demand in units of GiB-month. Storage prices vary across providers and [regions]({% link cockroachcloud/regions.md %}). Storage is charged based on the logical amount of data in the database. - **3 replicas included**: - CockroachDB {{ site.data.products.standard }} maintains at minimum three replicas of your data at no additional cost. For a cluster with more than three replicas, storage for each additional replica is priced at the storage price for the region. From c49e526807a931f13948441d043e10fa28565b22 Mon Sep 17 00:00:00 2001 From: Matt Linville Date: Mon, 23 Sep 2024 15:48:20 -0700 Subject: [PATCH 06/16] Add Standard and a couple missing preview features to FA page --- src/current/cockroachcloud/index.md | 8 ++++---- .../v23.1/cockroachdb-feature-availability.md | 12 ++++++++++++ .../v23.2/cockroachdb-feature-availability.md | 12 ++++++++++++ .../v24.1/cockroachdb-feature-availability.md | 12 ++++++++++++ .../v24.2/cockroachdb-feature-availability.md | 4 ++++ 5 files changed, 44 insertions(+), 4 deletions(-) diff --git a/src/current/cockroachcloud/index.md b/src/current/cockroachcloud/index.md index fdf61483ea6..8fb5b5d60d8 100644 --- a/src/current/cockroachcloud/index.md +++ b/src/current/cockroachcloud/index.md @@ -17,13 +17,13 @@ To get started right away, you can [sign up for a CockroachDB {{ site.data.produ When you create a cluster in CockroachDB {{ site.data.products.cloud }}, you select its plan. A CockroachDB {{ site.data.products.cloud }} organization can include clusters of each plan. This section provides an overview of each plan. For a more detailed comparison, refer to [Compare plans](#compare-plans). -- **CockroachDB {{ site.data.products.basic }}**: TODO +- **CockroachDB {{ site.data.products.basic }}**: Usage-based. CockroachDB Serverless clusters are now on CockroachDB {{ site.data.products.basic }}. -- **CockroachDB {{ site.data.products.standard }}**: TODO +- **CockroachDB {{ site.data.products.standard }}**: A new plan in [Preview]({% link {{ site.current_cloud_version}}/cockroachdb-feature-availability.md %}#features-in-preview). Compute for CockroachDB {{ site.data.products.standard }} is pre-provisioned and storage is usage-based. You can easily switch a CockroachDB {{ site.data.products.basic }} cluster to CockroachDB {{ site.data.products.standard }} in place. -- ** CockroachDB {{ site.data.products.advanced }}**: TODO +- **CockroachDB {{ site.data.products.advanced }}**: Fully pre-provisioned, with additional security and compliance features. CockroachDB Dedicated clusters are now on CockroachDB {{ site.data.products.advanced }}. CockroachDB Dedicated Advanced clusters are now on CockroachDB {{ site.data.products.advanced }} with enhanced security features enabled. -## Compare plans +### Compare plans This section summarizes key details about each plan to help you make the best choice for each cluster and its workload. For more details, refer to: diff --git a/src/current/v23.1/cockroachdb-feature-availability.md b/src/current/v23.1/cockroachdb-feature-availability.md index 95ed5d97e4b..834cfd2c495 100644 --- a/src/current/v23.1/cockroachdb-feature-availability.md +++ b/src/current/v23.1/cockroachdb-feature-availability.md @@ -43,6 +43,18 @@ General availability (GA) | Feature is production-ready and [Organizing CockroachDB {{ site.data.products.cloud }} clusters using folders]({% link cockroachcloud/folders.md %}) is in preview. Folders allow you to organize and manage access to your clusters according to your organization's requirements. For example, you can create top-level folders for each business unit in your organization, and within those folders, organize clusters by geographic location and then by level of maturity, such as production, staging, and testing. +### CockroachDB Standard + +CockroachDB Standard is a new plan for CockroachDB {{ site.data.products.cloud }} clusters and is in [Preview]({% link {{ site.current_cloud_version}}/cockroachdb-feature-availability.md %}#features-in-preview). Compute for CockroachDB {{ site.data.products.standard }} is pre-provisioned and storage is usage-based. You can easily switch a CockroachDB {{ site.data.products.basic }} cluster to CockroachDB {{ site.data.products.standard }} in place. + +### GCP Private Service Connect for CockroachDB Advanced + +[Connecting privately to a CockroachDB {{ site.data.products.advanced }} cluster using GCP Private Service Connect]({% link cockroachcloud/connect-to-your-cluster.md %}#gcp-private-service-connect) is in preview. Private Service Connect allows you to selectively connect your cluster deployed on GCP to a VPC within your Google Cloud project. + +### Azure Private Link for CockroachDB Advanced + +[Connecting privately to a CockroachDB {{ site.data.products.advanced }} cluster using Azure Private Link]({% link cockroachcloud/connect-to-your-cluster.md %}#azure-private-link) is in preview. Azure Private Link allows you to selectively connect your cluster deployed on Azure to a virtual network within your Azure tenant. + ### Custom Metrics Chart page for CockroachDB {{ site.data.products.cloud }} clusters The [**Custom Metrics Chart** page]({% link cockroachcloud/custom-metrics-chart-page.md %}) for CockroachDB {{ site.data.products.cloud }} clusters allows you to create custom charts showing the time series data for an available metric or combination of metrics. diff --git a/src/current/v23.2/cockroachdb-feature-availability.md b/src/current/v23.2/cockroachdb-feature-availability.md index 11f7da66871..d284d63dea8 100644 --- a/src/current/v23.2/cockroachdb-feature-availability.md +++ b/src/current/v23.2/cockroachdb-feature-availability.md @@ -47,6 +47,18 @@ Any feature made available in a phase prior to GA is provided without any warran [Organizing CockroachDB {{ site.data.products.cloud }} clusters using folders]({% link cockroachcloud/folders.md %}) is in preview. Folders allow you to organize and manage access to your clusters according to your organization's requirements. For example, you can create top-level folders for each business unit in your organization, and within those folders, organize clusters by geographic location and then by level of maturity, such as production, staging, and testing. +### CockroachDB Standard + +CockroachDB Standard is a new plan for CockroachDB {{ site.data.products.cloud }} clusters and is in [Preview]({% link {{ site.current_cloud_version}}/cockroachdb-feature-availability.md %}#features-in-preview). Compute for CockroachDB {{ site.data.products.standard }} is pre-provisioned and storage is usage-based. You can easily switch a CockroachDB {{ site.data.products.basic }} cluster to CockroachDB {{ site.data.products.standard }} in place. + +### GCP Private Service Connect for CockroachDB Advanced + +[Connecting privately to a CockroachDB {{ site.data.products.advanced }} cluster using GCP Private Service Connect]({% link cockroachcloud/connect-to-your-cluster.md %}#gcp-private-service-connect) is in preview. Private Service Connect allows you to selectively connect your cluster deployed on GCP to a VPC within your Google Cloud project. + +### Azure Private Link for CockroachDB Advanced + +[Connecting privately to a CockroachDB {{ site.data.products.advanced }} cluster using Azure Private Link]({% link cockroachcloud/connect-to-your-cluster.md %}#azure-private-link) is in preview. Azure Private Link allows you to selectively connect your cluster deployed on Azure to a virtual network within your Azure tenant. + ### Custom Metrics Chart page for CockroachDB {{ site.data.products.cloud }} clusters The [**Custom Metrics Chart** page]({% link cockroachcloud/custom-metrics-chart-page.md %}) for CockroachDB {{ site.data.products.cloud }} clusters allows you to create custom charts showing the time series data for an available metric or combination of metrics. diff --git a/src/current/v24.1/cockroachdb-feature-availability.md b/src/current/v24.1/cockroachdb-feature-availability.md index da495648ffc..04f01b59d43 100644 --- a/src/current/v24.1/cockroachdb-feature-availability.md +++ b/src/current/v24.1/cockroachdb-feature-availability.md @@ -47,6 +47,18 @@ Any feature made available in a phase prior to GA is provided without any warran [Organizing CockroachDB {{ site.data.products.cloud }} clusters using folders]({% link cockroachcloud/folders.md %}) is in preview. Folders allow you to organize and manage access to your clusters according to your organization's requirements. For example, you can create top-level folders for each business unit in your organization, and within those folders, organize clusters by geographic location and then by level of maturity, such as production, staging, and testing. +### CockroachDB Standard + +CockroachDB Standard is a new plan for CockroachDB {{ site.data.products.cloud }} clusters and is in [Preview]({% link {{ site.current_cloud_version}}/cockroachdb-feature-availability.md %}#features-in-preview). Compute for CockroachDB {{ site.data.products.standard }} is pre-provisioned and storage is usage-based. You can easily switch a CockroachDB {{ site.data.products.basic }} cluster to CockroachDB {{ site.data.products.standard }} in place. + +### GCP Private Service Connect for CockroachDB Advanced + +[Connecting privately to a CockroachDB {{ site.data.products.advanced }} cluster using GCP Private Service Connect]({% link cockroachcloud/connect-to-your-cluster.md %}#gcp-private-service-connect) is in preview. Private Service Connect allows you to selectively connect your cluster deployed on GCP to a VPC within your Google Cloud project. + +### Azure Private Link for CockroachDB Advanced + +[Connecting privately to a CockroachDB {{ site.data.products.advanced }} cluster using Azure Private Link]({% link cockroachcloud/connect-to-your-cluster.md %}#azure-private-link) is in preview. Azure Private Link allows you to selectively connect your cluster deployed on Azure to a virtual network within your Azure tenant. + ### GCP Private Service Connect for CockroachDB Advanced [Connecting privately to a CockroachDB {{ site.data.products.advanced }} cluster using GCP Private Service Connect]({% link cockroachcloud/connect-to-your-cluster.md %}#gcp-private-service-connect) is in preview. Private Service Connect allows you to selectively connect your cluster deployed on GCP to a VPC within your Google Cloud project. diff --git a/src/current/v24.2/cockroachdb-feature-availability.md b/src/current/v24.2/cockroachdb-feature-availability.md index 15203391e31..17729959762 100644 --- a/src/current/v24.2/cockroachdb-feature-availability.md +++ b/src/current/v24.2/cockroachdb-feature-availability.md @@ -55,6 +55,10 @@ The [`VECTOR`]({% link {{ page.version.version }}/vector.md %}) data type stores [Organizing CockroachDB {{ site.data.products.cloud }} clusters using folders]({% link cockroachcloud/folders.md %}) is in preview. Folders allow you to organize and manage access to your clusters according to your organization's requirements. For example, you can create top-level folders for each business unit in your organization, and within those folders, organize clusters by geographic location and then by level of maturity, such as production, staging, and testing. +### CockroachDB Standard + +CockroachDB Standard is a new plan for CockroachDB {{ site.data.products.cloud }} clusters and is in [Preview]({% link {{ site.current_cloud_version}}/cockroachdb-feature-availability.md %}#features-in-preview). Compute for CockroachDB {{ site.data.products.standard }} is pre-provisioned and storage is usage-based. You can easily switch a CockroachDB {{ site.data.products.basic }} cluster to CockroachDB {{ site.data.products.standard }} in place. + ### GCP Private Service Connect for CockroachDB Advanced [Connecting privately to a CockroachDB {{ site.data.products.advanced }} cluster using GCP Private Service Connect]({% link cockroachcloud/connect-to-your-cluster.md %}#gcp-private-service-connect) is in preview. Private Service Connect allows you to selectively connect your cluster deployed on GCP to a VPC within your Google Cloud project. From 677a015648e50fd06e4573c4aac1e1b6a7636d2e Mon Sep 17 00:00:00 2001 From: Matt Linville Date: Mon, 23 Sep 2024 15:52:44 -0700 Subject: [PATCH 07/16] Fix metrics links --- src/current/cockroachcloud/index.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/src/current/cockroachcloud/index.md b/src/current/cockroachcloud/index.md index 8fb5b5d60d8..9a7e39ed8c8 100644 --- a/src/current/cockroachcloud/index.md +++ b/src/current/cockroachcloud/index.md @@ -62,20 +62,20 @@ This section summarizes key details about each plan to help you make the best ch
- - + + - - + + - - + +
Managed backup storage Daily backups included in Request Unit costsUsage-based, varies per cloud provider and region.

Currently not charged during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics.md %}#backup-and-restore).		Usage-based, varies per cloud provider and region.

Currently not charged during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics.md %}#backup-and-restore).		Usage-based, varies per cloud provider and region.

Currently not charged during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics-self-hosted.md %}#backup-and-restore).		Usage-based, varies per cloud provider and region.

Currently not charged during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics-self-hosted.md %}#backup-and-restore).
[Data transfer](#data-transfer) Usage-based via Request UnitsUsage-based; cloud provider list price

Currently not charged during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics.md %}#backup-and-restore)		Usage-based; cloud provider list price

Currently not charged during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics.md %}#backup-and-restore)		Usage-based; cloud provider list price

Currently not charged during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics-self-hosted.md %}#backup-and-restore)		Usage-based; cloud provider list price

Currently not charged during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics-self-hosted.md %}#backup-and-restore)
[Change Data Capture]({% link {{site.current_cloud_version}}/change-data-capture-overview.md %}) Usage-based via Request UnitsUsage-based.

Currently not charged during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics.md %}#backup-and-restore)		Usage-based.

Currently not charged during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics.md %}#backup-and-restore)		Usage-based.

Currently not charged during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics-self-hosted.md %}#backup-and-restore)		Usage-based.

Currently not charged during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics-self-hosted.md %}#backup-and-restore)
@@ -125,7 +125,7 @@ Refer to [Pricing](https://www.cockroachlabs.com/pricing/). ### Storage {{site.data.alerts.callout_info}} -There is no charge for backup storage during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics.md %}#backup-and-restore) +There is no charge for backup storage during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics-self-hosted.md %}#backup-and-restore) {{site.data.alerts.end}}
@@ -160,7 +160,7 @@ Hourly storage charges are accumulated throughout the month to determine the tot ### Data transfer {{site.data.alerts.callout_info}} -There is no charge for data transfer during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics.md %}#backup-and-restore) +There is no charge for data transfer during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics-self-hosted.md %}#backup-and-restore) {{site.data.alerts.end}}
@@ -203,7 +203,7 @@ For CockroachDB {{ site.data.products.advanced }}, data transfer is billed based All CockroachDB {{ site.data.products.cloud }} clusters can use [Enterprise Changefeeds](% link {{ site.current_cloud_version}}/how-does-an-enterprise-changefeed-work.md %). {{site.data.alerts.callout_info}} -There is no charge for changefeeds during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics.md %}#backup-and-restore) +There is no charge for changefeeds during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics-self-hosted.md %}#backup-and-restore) {{site.data.alerts.end}}
From dfa87f21601cc311dd0ea418eba7279f6a6bd580 Mon Sep 17 00:00:00 2001 From: Matt Linville Date: Mon, 23 Sep 2024 16:21:28 -0700 Subject: [PATCH 08/16] Fix another link --- src/current/cockroachcloud/plan-your-cluster.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/current/cockroachcloud/plan-your-cluster.md b/src/current/cockroachcloud/plan-your-cluster.md index 02ba48a5260..ae76bcc7949 100644 --- a/src/current/cockroachcloud/plan-your-cluster.md +++ b/src/current/cockroachcloud/plan-your-cluster.md @@ -31,7 +31,7 @@ To achieve a rough initial estimate of compute capacity, consider: - **Multi-region deployments**: The provisioned capacity of your cluster applies to the entire cluster, regardless of the number of nodes or regional topography. The provisioned capacity is effectively a budget for the cluster that can be used by a node in any region to meet its compute demand. This simplifies planning compute capacity for multi-region deployments. The overall [compute capacity cost]({% link cockroachcloud/billing-management.md %}) for a multi-region CockroachDB {{ site.data.products.standard }} cluster is calculated based on the price of the most expensive region in the cluster. -After considering the above factors, you have enough information to [create a CockroachDB {{ site.data.products.standard }} cluster]({% link cockroachcloud/create-your-cluster.md %}) using the CockroachDB {{ site.data.products.cloud }} Console or the [CockroachDB Terraform provider]({% link cockroachcloud/provision-a-cluster-using-terraform.md %}). After the cluster is deployed, you can [scale its compute capacity]({% link cockroachcloud/cluster-management.md %}#edit-cluster-capacity) by increasing or decreasing its provisioned capacity as needed. +After considering the above factors, you have enough information to [create a CockroachDB {{ site.data.products.standard }} cluster]({% link cockroachcloud/create-your-cluster.md %}) using the CockroachDB {{ site.data.products.cloud }} Console or the [CockroachDB Terraform provider]({% link cockroachcloud/provision-a-cluster-with-terraform.md %}). After the cluster is deployed, you can [scale its compute capacity]({% link cockroachcloud/cluster-management.md %}#edit-cluster-capacity) by increasing or decreasing its provisioned capacity as needed. {{site.data.alerts.callout_success}} You can decrease the provisioned capacity only three times within a 7-day period. You can increase the provisioned capacity at any time. From d4ecbbca1d9ed078339a74d0c987eeb9184e474e Mon Sep 17 00:00:00 2001 From: Matt Linville Date: Mon, 23 Sep 2024 16:31:28 -0700 Subject: [PATCH 09/16] Fix more links --- src/current/cockroachcloud/plan-your-cluster.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/current/cockroachcloud/plan-your-cluster.md b/src/current/cockroachcloud/plan-your-cluster.md index ae76bcc7949..21808deeb88 100644 --- a/src/current/cockroachcloud/plan-your-cluster.md +++ b/src/current/cockroachcloud/plan-your-cluster.md @@ -102,5 +102,5 @@ If you add a 6th replica, the cluster will consume 3000 GiB (500 x 6), and will - [Create a CockroachDB {{ site.data.products.standard }} cluster]({% link cockroachcloud/create-your-cluster.md %}) - [Edit cluster capacity]({% link cockroachcloud/cluster-management.md %}#edit-cluster-capacity) -- [Plan an CockroachDB {{ site.data.products.advanced }} cluster]({% link cockroachcloud/plan-an-advanced-cluster.md %}) -- [Plan an CockroachDB {{ site.data.products.basic }} cluster]({% link cockroachcloud/plan-a-basic-cluster.md %}) +- [Plan an CockroachDB {{ site.data.products.advanced }} cluster]({% link cockroachcloud/plan-your-cluster-advanced.md %}) +- [Plan an CockroachDB {{ site.data.products.basic }} cluster]({% link cockroachcloud/plan-your-cluster-basic.md %}) From 654c88dc6fa1f337c93892cc8754997caa91f51e Mon Sep 17 00:00:00 2001 From: Matt Linville Date: Mon, 23 Sep 2024 16:35:26 -0700 Subject: [PATCH 10/16] Enable TOC on Cloud landing page --- src/current/cockroachcloud/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/current/cockroachcloud/index.md b/src/current/cockroachcloud/index.md index 9a7e39ed8c8..158fe967619 100644 --- a/src/current/cockroachcloud/index.md +++ b/src/current/cockroachcloud/index.md @@ -1,7 +1,7 @@ --- title: CockroachDB Cloud docs summary: Learn more about CockroachDB Cloud, a fully-managed service created and owned by Cockroach Labs that makes deploying, scaling, and managing CockroachDB effortless. -toc: false +toc: true contribute: false cta: false homepage: false From 691bdf129f2a88b2f2a201382c7c77fac9bbd0aa Mon Sep 17 00:00:00 2001 From: Matt Linville Date: Mon, 23 Sep 2024 16:37:27 -0700 Subject: [PATCH 11/16] Add Cloud landing page to left-hand nav --- .../_includes/v24.2/sidebar-data/cloud-deployments.json | 6 ++++++ src/current/cockroachcloud/index.md | 3 ++- 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/src/current/_includes/v24.2/sidebar-data/cloud-deployments.json b/src/current/_includes/v24.2/sidebar-data/cloud-deployments.json index 5978abe7fe6..9d28656668b 100644 --- a/src/current/_includes/v24.2/sidebar-data/cloud-deployments.json +++ b/src/current/_includes/v24.2/sidebar-data/cloud-deployments.json @@ -2,6 +2,12 @@ "title": "Cloud Deployments", "is_top_level": true, "items": [ + { + "title": "Overview", + "urls": [ + "/cockroachcloud/index.html" + ] + }, { "title": "Create an Account", "urls": [ diff --git a/src/current/cockroachcloud/index.md b/src/current/cockroachcloud/index.md index 158fe967619..936ebd5ad0c 100644 --- a/src/current/cockroachcloud/index.md +++ b/src/current/cockroachcloud/index.md @@ -7,7 +7,8 @@ cta: false homepage: false --- -## Overview + +## CockroachDB Cloud Overview CockroachDB {{ site.data.products.cloud }} is a fully-managed service run by Cockroach Labs, which simplifies deployment and management of CockroachDB deployments. This page provides an introduction to CockroachDB {{ site.data.products.cloud }} provides an overview of each type of cluster: CockroachDB {{ site.data.products.standard }}, CockroachDB {{ site.data.products.basic }}, and CockroachDB {{ site.data.products.advanced }}. From 4bde52221328f53a19f52510044fee56940a3715 Mon Sep 17 00:00:00 2001 From: Matt Linville Date: Mon, 23 Sep 2024 17:41:51 -0700 Subject: [PATCH 12/16] Fix some more links --- src/current/cockroachcloud/index.md | 4 ++-- src/current/cockroachcloud/plan-your-cluster.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/current/cockroachcloud/index.md b/src/current/cockroachcloud/index.md index 936ebd5ad0c..8e1ebe0e62d 100644 --- a/src/current/cockroachcloud/index.md +++ b/src/current/cockroachcloud/index.md @@ -201,7 +201,7 @@ For CockroachDB {{ site.data.products.advanced }}, data transfer is billed based ### Changefeeds -All CockroachDB {{ site.data.products.cloud }} clusters can use [Enterprise Changefeeds](% link {{ site.current_cloud_version}}/how-does-an-enterprise-changefeed-work.md %). +All CockroachDB {{ site.data.products.cloud }} clusters can use [Enterprise Changefeeds]({% link {{ site.current_cloud_version}}/how-does-an-enterprise-changefeed-work.md %}). {{site.data.alerts.callout_info}} There is no charge for changefeeds during [Usage-based backup metrics Preview]({% link {{ site.current_cloud_version}}/essential-metrics-self-hosted.md %}#backup-and-restore) @@ -236,7 +236,7 @@ In CockroachDB {{ site.data.products.standard }}, Change Data Capture is billed ## Usage-based metrics in Preview -Usage-based metrics for [data transfer](#data-transfer), [managed backup storage](#storage), and [Change Data Capture](#change-data-capture) are in [Preview]({% link {{site.current_cloud_version }}/cockroachdb-feature-availability.md %}#features-in-preview). You can view the usage of these metrics in your invoice page under **Billing**. +Usage-based metrics for [data transfer](#data-transfer), [managed backup storage](#storage), and [changefeeds](#changefeeds) are in [Preview]({% link {{site.current_cloud_version }}/cockroachdb-feature-availability.md %}#features-in-preview). You can view the usage of these metrics in your invoice page under **Billing**. There will be no additional charges for these metrics during the preview period, which is in effect until December, 2024. During this time, charges will appear as $0 on your monthly invoice. diff --git a/src/current/cockroachcloud/plan-your-cluster.md b/src/current/cockroachcloud/plan-your-cluster.md index 21808deeb88..e50ef360c88 100644 --- a/src/current/cockroachcloud/plan-your-cluster.md +++ b/src/current/cockroachcloud/plan-your-cluster.md @@ -55,7 +55,7 @@ Important capacity and pricing policies mentioned elsewhere are summarized here: ### More details about capacity -We recommend that you start with [Quickstart: Provisioning and adjusting capacity](#quickstart-provision-and-adjusting-capacity) to arrive at the best initial compute capacity for your workload and that you adjust the cluster's capacity over time as the workload evolves. In addition, consider the following: +We recommend that you start with [Quickstart: Provision and adjust capacity](#quickstart-provision-and-adjust-capacity) to arrive at the best initial compute capacity for your workload and that you adjust the cluster's capacity over time as the workload evolves. In addition, consider the following: - **Smaller workloads**: CockroachDB {{ site.data.products.standard }} is well suited for workloads that require 12 or fewer vCPUs. By contrast, 12 vCPUs (3 nodes x 4 vCPUs) is the minimum configuration for CockroachDB {{ site.data.products.advanced }}. @@ -71,7 +71,7 @@ We recommend that you start with [Quickstart: Provisioning and adjusting capacit - **Workloads with advanced security or compliance requirements**: For workloads subject to advanced security or compliance requirements, consider CockroachDB {{ site.data.products.advanced }}, which complies with [PCI DSS and HIPAA]({% link cockroachcloud/pci-dss.md %}). To learn more refer to [Compliance in CockroachDB {{ site.data.products.cloud }}]({% link cockroachcloud/compliance.md %}). -For more details to help you compare CockroachDB {{ site.data.products.cloud }} cluster plans, refer to [TBD COMPARISON PAGE](/). +For more details to help you compare CockroachDB {{ site.data.products.cloud }} cluster plans, refer to [CockroachDB {{ site.data.products.cloud }} Overview]({% link cockroachcloud/index.md %}). ## Storage pricing From 372a46d284c2dca51e0142f5c6505d5a093e7c74 Mon Sep 17 00:00:00 2001 From: Matt Linville Date: Mon, 23 Sep 2024 17:53:47 -0700 Subject: [PATCH 13/16] Fix another link --- src/current/cockroachcloud/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/current/cockroachcloud/index.md b/src/current/cockroachcloud/index.md index 8e1ebe0e62d..e2ef1b69507 100644 --- a/src/current/cockroachcloud/index.md +++ b/src/current/cockroachcloud/index.md @@ -44,7 +44,7 @@ This section summarizes key details about each plan to help you make the best ch [Compute](#compute) - Usage-based via [Request Units]({% link cockroachcloud/create-a-basic-cluster.md %}#step-4-edit-cluster-capacity) + Usage-based via [Request Units]({% link cockroachcloud/create-a-basic-cluster.md %}#step-4-configure-cluster-capacity) Provisioned; cost per hour based on [vCPU quantity, cloud provider, and regions]({% link cockroachcloud/create-your-cluster.md %}#step-4-provision-cluster-capacity). Provisioned; cost per hour per node based on [vCPU quantity, cloud provider, and region]({% link cockroachcloud/create-an-advanced-cluster.md %}#step-5-configure-cluster-capacity) From 1d5d5f442d32d5e825bbc7621307681ae0426c3b Mon Sep 17 00:00:00 2001 From: "Matt Linville (he/him)" Date: Mon, 23 Sep 2024 18:09:59 -0700 Subject: [PATCH 14/16] Update src/current/cockroachcloud/index.md --- src/current/cockroachcloud/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/current/cockroachcloud/index.md b/src/current/cockroachcloud/index.md index e2ef1b69507..ea5ec7d381d 100644 --- a/src/current/cockroachcloud/index.md +++ b/src/current/cockroachcloud/index.md @@ -133,7 +133,7 @@ There is no charge for backup storage during [Usage-based backup metrics Preview Storage for CockroachDB {{ site.data.products.basic }} is automatically provisioned on demand, eliminating the need for manual management. Costs are based on actual usage and adjust dynamically as data is added or removed, starting from zero. -Storage is billed hourly, with [rates](https://www.cockroachlabs.com/pricing) depending on the cloud provider and the region where the cluster is hosted.{% comment %}TODO: Resolve this contradiction. https://cockroachlabs.slack.com/archives/C05KHQULKFB/p1726955009576009{% endcomment %} +Storage is billed hourly. Refer to [Pricing](https://www.cockroachlabs.com/pricing).
From 160643fa6d6cec5e1540e63304c4ccc74544744a Mon Sep 17 00:00:00 2001 From: "Matt Linville (he/him)" Date: Tue, 24 Sep 2024 20:00:23 -0700 Subject: [PATCH 15/16] Update src/current/cockroachcloud/basic-cluster-management.md --- src/current/cockroachcloud/basic-cluster-management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/current/cockroachcloud/basic-cluster-management.md b/src/current/cockroachcloud/basic-cluster-management.md index 1fba2212e39..f7945ec89dd 100644 --- a/src/current/cockroachcloud/basic-cluster-management.md +++ b/src/current/cockroachcloud/basic-cluster-management.md @@ -35,7 +35,7 @@ The monthly cost estimate is calculated using simple extrapolation that assumes ## Edit cluster capacity -The price-performance characteristics of CockroachDB {{ site.data.products.basic }} vary significantly depending on the workload. It can be difficult to estimate a workload's compute requirements in advance. To increase or decrease a cluster's capacity: +The price-performance characteristics of CockroachDB {{ site.data.products.basic }} vary significantly depending on the workload. It can be difficult to estimate a workload's compute requirements in advance. With {{ site.data.products.basic }}, by default compute and storage scale with your cluster's needs, but you can limit a cluster's resource usage: 1. In the **Capacity used this month** section of your cluster's [**Overview** page]({% link cockroachcloud/cluster-overview-page.md %}), click **Update capacity**. From 9a82e652c1976512ca2a77d00714b8cfb9b4af08 Mon Sep 17 00:00:00 2001 From: "Matt Linville (he/him)" Date: Tue, 24 Sep 2024 23:31:38 -0700 Subject: [PATCH 16/16] Apply suggestions from code review Co-authored-by: Mike Lewis <76072290+mikeCRL@users.noreply.github.com> --- .../cockroachcloud/plan-your-cluster.md | 24 +++++++++---------- 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/src/current/cockroachcloud/plan-your-cluster.md b/src/current/cockroachcloud/plan-your-cluster.md index e50ef360c88..c030dec2539 100644 --- a/src/current/cockroachcloud/plan-your-cluster.md +++ b/src/current/cockroachcloud/plan-your-cluster.md @@ -14,7 +14,7 @@ This page provides guidance for planning and estimating costs for a CockroachDB The compute resources available to a CockroachDB {{ site.data.products.standard }} cluster is provisioned and scaled using a capacity model measured in _virtual CPUs (vCPUs)_. A cluster's capacity requirements depend on the scale and query profile of the cluster's workload, and may change over time as the workload evolves. It’s typical to estimate the initial compute capacity needed for a workload before creating the cluster, and to adjust the capacity up or down based observation of the workload's consumption. -Storage for a CockroachDB {{ site.data.products.standard }} cluster is allocated on demand and is not covered in this section. Refer to [Storage](#storage-pricing) +Storage for a CockroachDB {{ site.data.products.standard }} cluster is allocated on demand and is not covered in this section. Refer to [Storage](#storage-pricing). ### Quickstart: Provision and adjust capacity @@ -27,11 +27,11 @@ To achieve a rough initial estimate of compute capacity, consider: - **Additional capacity buffer**: To accommodate unanticipated load and mitigate the risk of application degradation if the cluster's capacity is exceeded, we recommend that you plan for additional capacity beyond your initial estimate. A 40% buffer is a good starting point, but more may be needed if the workload is unpredictable or highly sensitive to query latency. Depending on the nature of the workload, such as when demand is seasonal, you can plan to scale the cluster's capacity temporarily to address the workload's requirements. - **Exceeding capacity limit**: CockroachDB {{ site.data.products.standard }} enforces the cluster's provisioned capacity, limiting application throughput if the workload exceeds the cluster's provisioned capacity. This can lead to increased query latency and degraded application performance. - - **Notifications to prevent overrun**: To help mitigate against the risk of exceeding a cluster's capacity, email and CockroachDB {{ site.data.products.cloud }} Console notifications will occur when a cluster workload exceeds 90% and 90% of its provisioned capacity. + - **Notifications to prevent overrun**: To help mitigate against the risk of exceeding a cluster's capacity, email and CockroachDB {{ site.data.products.cloud }} Console notifications will occur when a cluster workload exceeds 70% and 90% of its provisioned capacity. - **Multi-region deployments**: The provisioned capacity of your cluster applies to the entire cluster, regardless of the number of nodes or regional topography. The provisioned capacity is effectively a budget for the cluster that can be used by a node in any region to meet its compute demand. This simplifies planning compute capacity for multi-region deployments. The overall [compute capacity cost]({% link cockroachcloud/billing-management.md %}) for a multi-region CockroachDB {{ site.data.products.standard }} cluster is calculated based on the price of the most expensive region in the cluster. -After considering the above factors, you have enough information to [create a CockroachDB {{ site.data.products.standard }} cluster]({% link cockroachcloud/create-your-cluster.md %}) using the CockroachDB {{ site.data.products.cloud }} Console or the [CockroachDB Terraform provider]({% link cockroachcloud/provision-a-cluster-with-terraform.md %}). After the cluster is deployed, you can [scale its compute capacity]({% link cockroachcloud/cluster-management.md %}#edit-cluster-capacity) by increasing or decreasing its provisioned capacity as needed. +After considering the above factors, you have enough information to [create a CockroachDB {{ site.data.products.standard }} cluster]({% link cockroachcloud/create-your-cluster.md %}) using the CockroachDB {{ site.data.products.cloud }} Console, the [CockroachDB Terraform provider]({% link cockroachcloud/provision-a-cluster-with-terraform.md %}), or the [CockroachDB Cloud API](cloud-api.md). After the cluster is deployed, you can [scale its compute capacity]({% link cockroachcloud/cluster-management.md %}#edit-cluster-capacity) by increasing or decreasing its provisioned capacity as needed. {{site.data.alerts.callout_success}} You can decrease the provisioned capacity only three times within a 7-day period. You can increase the provisioned capacity at any time. @@ -43,7 +43,7 @@ The CockroachDB {{ site.data.products.cloud }} Console provides insight into you Important capacity and pricing policies mentioned elsewhere are summarized here: -- **Minimum and maximum provisioned capacity**: - A CockroachDB {{ site.data.products.standard }} cluster must have a provisioned capacity of at minimum 2 vCPUs. For production workloads, we recommend at minimum 4 to 8 vCPUs. The maximum capacity for CockroachDB {{ site.data.products.standard }} is 60 vCPUs. To express interest in higher-capacity clusters, [talk to an expert](https://www.cockroachlabs.com/contact/). +- **Minimum and maximum provisioned capacity**: A CockroachDB {{ site.data.products.standard }} cluster must have a provisioned capacity of at minimum 2 vCPUs. For production workloads, we recommend at minimum 4 to 8 vCPUs. The maximum capacity for CockroachDB {{ site.data.products.standard }} is 60 vCPUs. To express interest in higher-capacity clusters, [talk to an expert](https://www.cockroachlabs.com/contact/). - **Enforcing provisioned capacity limits**: CockroachDB {{ site.data.products.cloud }} enforces the cluster’s provisioned capacity, limiting application throughput if the workload exceeds the capacity limit. This can result in degraded performance and increased query latency. You can increase a cluster's capacity at any time. @@ -60,12 +60,12 @@ We recommend that you start with [Quickstart: Provision and adjust capacity](#qu - **Smaller workloads**: CockroachDB {{ site.data.products.standard }} is well suited for workloads that require 12 or fewer vCPUs. By contrast, 12 vCPUs (3 nodes x 4 vCPUs) is the minimum configuration for CockroachDB {{ site.data.products.advanced }}. CockroachDB {{ site.data.products.standard }} is not recommended for: - - Analytical workloads that involve a large quantity of large, complex reads - - OLAP or hybrid OLTP/OLAP applications +- **Analytical workloads that involve many large, complex reads** +- **OLAP or hybrid OLTP/OLAP applications** - **Asymmetric multi-region workloads**: Often, multi-region deployments are asymmetric in terms of CPU utilization across regions. For example, in a three-region cluster, two of the three regions may require more capacity than the third, or vice versa. In CockroachDB {{ site.data.products.standard }}, a cluster's compute capacity is available in all regions. - For workloads that require symmetric capacity per region or where a given region must maintain a given compute capacity, CockroachDB {{ site.data.products.advanced }} may be a better option. + For workloads that require asymmetric capacity per region or where a given region must maintain a given compute capacity, CockroachDB {{ site.data.products.advanced }} may be a better option. - **Workloads that are sensitive to latency**: CockroachDB {{ site.data.products.standard }} clusters use a different networking architecture than CockroachDB {{ site.data.products.advanced }}. This architecture can introduce additional query latency of around 1 microsecond when compared with CockroachDB {{ site.data.products.advanced }}. @@ -76,11 +76,11 @@ For more details to help you compare CockroachDB {{ site.data.products.cloud }} ## Storage pricing Storage capacity for a CockroachDB {{ site.data.products.standard }} cluster is [priced]({% link cockroachcloud/billing-management.md %}) on demand in units of GiB-month. Storage prices vary across providers and [regions]({% link cockroachcloud/regions.md %}). Storage is charged based on the logical amount of data in the database. -- **3 replicas included**: - CockroachDB {{ site.data.products.standard }} maintains at minimum three replicas of your data at no additional cost. + - **3 replicas included**: CockroachDB {{ site.data.products.standard }} maintains at minimum three replicas of your data at no additional cost. - For a cluster with more than three replicas, storage for each additional replica is priced at the storage price for the region. + For a cluster with more than three replicas, storage for each additional replica is priced at the storage price for the region. -- **Multi-region storage**: In a multi-region cluster, storage prices vary by region. The data in each region is priced at that region's storage rate. + - **Multi-region storage**: In a multi-region cluster, storage prices vary by region. The data in each region is priced at that region's storage rate. ### Single-region example @@ -88,11 +88,11 @@ By default, CockroachDB {{ site.data.products.cloud }} maintains three replicas For example, if a single-region cluster is deployed in `us-central-1` and contains 500 GiB of data. CockroachDB {{ site.data.products.cloud }} stores three replicas, for a total of 1500 GiB of data. However, you are billed only for 500 GiB of storage. -If you add a fourth replicas, the cluster consumes 2000 GiB of storage (500 x 4), but you are billed only for 1000 GiB (500 for the data and 500 for the fourth replica). +If you add a fourth replica, the cluster consumes 2000 GiB of storage (500 x 4), but you are billed only for 1000 GiB (500 for the data and 500 for the fourth replica). ### Multi-region example -For multi-region clusters, we recommend 5 or more replicas are typically maintained across availability zones and regions for resilience against both zone and region failure. The first three replicas are included in the base storage price, while additional replicas are priced based on the ratio of additional regions to the initial three. +For multi-region clusters, we recommend that 5 or more replicas are maintained across availability zones and regions for resilience against both zone and region failure. The first three replicas are included in the base storage price, while additional replicas are priced based on the ratio of additional regions to the initial three. Consider the example of a three-region cluster with 500 GiB of logical data, deployed in `us-central1`, `us-west2`, and `europe-west1`, with 5 replicas. The logical data and the first three replicas are included in the monthly storage cost. The additional two replicas are charged at 2/3 of the monthly storage cost. This cluster consumes 2500 GiB of storage, but is billed for 1500 GiB for the initial data and 3 replicas, plus 2/3 of the additional 1000 GiB for the additional two replicas (2 replicas beyond the initial 3).