diff --git a/src/current/cockroachcloud/costs.md b/src/current/cockroachcloud/costs.md index 900255d6bda..ca4424a3cde 100644 --- a/src/current/cockroachcloud/costs.md +++ b/src/current/cockroachcloud/costs.md @@ -5,70 +5,28 @@ toc: true keywords: pricing --- -The cost structure for a CockroachDB Cloud organization depends on its deployment types, which correspond to CockroachDB Cloud plans. +The ways that monthly charges are incurred for a CockroachDB Cloud organization depend on the plans of its clusters: CockroachDB Basic, Standard, or Advanced. This page explains costs under each plan, specifying components that are billed based on provisioned capacity or usage. -This page applies to CockroachDB Cloud clusters as of October 1, 2024. +Refer to [CockroachDB Pricing](https://www.cockroachlabs.com/pricing/) for details on plans and rates. -## Costs across CockroachDB Cloud plans - -For specific rates and feature comparisons, refer to the [Pricing](https://www.cockroachlabs.com/pricing/) page. - -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: +For details on planning or provisioning clusters, refer to: - [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-your-cluster-advanced.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-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)
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]({% link cockroachcloud/managed-backups.md %}) storageDaily backups included in Request Unit costsUsage-based, varies per cloud provider and region.

Currently not charged during [Usage-based billing metrics Preview](#usage-based-billing-metrics-in-preview).		Usage-based, varies per cloud provider and region.

Currently not charged during [Usage-based billing metrics Preview](#usage-based-billing-metrics-in-preview).
[Data transfer](#data-transfer)Usage-based via Request UnitsUsage-based; cloud provider list price

Currently not charged during [Usage-based billing metrics Preview](#usage-based-billing-metrics-in-preview)		Usage-based; cloud provider list price

Currently not charged during [Usage-based billing metrics Preview](#usage-based-billing-metrics-in-preview)
[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 billing metrics Preview](#usage-based-billing-metrics-in-preview)		Usage-based.

Currently not charged during [Usage-based billing metrics Preview](#usage-based-billing-metrics-in-preview)
- -To learn more about pricing in CockroachDB {{ site.data.products.cloud }}, refer to [Pricing](https://www.cockroachlabs.com/pricing/). +## Costs across CockroachDB Cloud plans + +This table summarizes key details about how costs are calculated for each plan to help you get started in choosing the one that best meets your needs for a given workload. + +| | CockroachDB Basic

Usage-based billing only | CockroachDB Standard

Provisioned compute, usage-based storage, data transfer, backups, and Change Data Capture (CDC) | CockroachDB 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-configure-cluster-capacity) | Provisioned; cost per hour based on plan, [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 plan, [vCPU quantity, cloud provider, region]({% link cockroachcloud/create-an-advanced-cluster.md %}#step-5-configure-cluster-capacity), and optional security add-on. | +| [Storage](#storage) | Usage-based | Usage-based; rates vary per cloud provider and region | Provisioned; billed per hour per node; rates vary per cloud provider, region, and optional security add-on | +| [IOPS](#iops) | Usage-based via Request Units | Included in storage costs | Provisioned based on storage and varies per cloud provider | +| [Backups](#backups) | Usage-based via Request Units | Usage-based.

[Managed Backups](https://www.cockroachlabs.com/docs/cockroachcloud/managed-backups) storage rates vary per cloud provider, region, and backup frequency.

[Self-Managed Backups](https://www.cockroachlabs.com/docs/cockroachcloud/take-and-restore-self-managed-backups) fee incurred per GiB transferred to your own object storage.

No charges for either backup type during the [Usage-based billing metrics Preview](#usage-based-billing-metrics-in-preview). | Usage-based.

[Managed Backups](https://www.cockroachlabs.com/docs/cockroachcloud/managed-backups) storage rates vary per cloud provider, region, and backup frequency.

[Self-Managed Backups](https://www.cockroachlabs.com/docs/cockroachcloud/take-and-restore-self-managed-backups) fee incurred per GiB transferred to your own object storage.

No charges for either backup type during the [Usage-based billing metrics Preview](#usage-based-billing-metrics-in-preview). | +| [Data transfer](#data-transfer) | Usage-based via Request Units | Usage-based; rates vary per cloud provider and data transfer type.

Currently not charged during [Usage-based billing metrics Preview](#usage-based-billing-metrics-in-preview). | Usage-based; rates vary per cloud provider and data transfer type.

Currently not charged during [Usage-based billing metrics Preview](#usage-based-billing-metrics-in-preview). | +| [Change Data Capture](#change-data-capture-changefeeds) | Usage-based via Request Units | Usage-based, per GiB-Hour watched across all changefeeds.

Currently not charged during [Usage-based billing metrics Preview](#usage-based-billing-metrics-in-preview). | Usage-based, per GiB-Hour watched across all changefeeds.

Currently not charged during [Usage-based billing metrics Preview](#usage-based-billing-metrics-in-preview). | ## More details @@ -84,19 +42,19 @@ This section supplements the details in [Costs across CockroachDB Cloud plans](#
-For CockroachDB {{ site.data.products.basic }}, compute is usage-based and calculated in Request Units. +For CockroachDB Basic, compute cost is usage-based through its consumption of [Request Units](https://www.cockroachlabs.com/docs/cockroachcloud/resource-usage-basic#understand-resource-consumption).
-Standard deployments have provisioned compute capacity where customers set a maximum processing capacity for their cluster, measured in vCPUs. This capacity represents the peak processing power the deployment can handle at any given time. +Standard clusters have provisioned compute capacity where customers set a maximum processing capacity for their cluster, measured in vCPUs. This capacity represents the peak processing power the cluster can handle at any given time. -The compute pricing is measured in vCPU-hour, 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. +A cluster’s compute charges are based on the cluster’s provisioned capacity in vCPU-hours, with rates that depend on the cluster’s cloud provider and regions. Billing is based on the capacity reserved, not the actual usage. Charges are accumulated throughout the month to determine the total monthly compute charges. -Note: In multi-region clusters, the price of the most expensive region is applied to the entire cluster’s compute capacity. +In a multi-region cluster, the price of the most expensive region is applied to the entire cluster’s compute capacity. -For example, consider a three region Multi-Region GCP deployment provisioned in Iowa (us-central1), St. Ghislain (europe-central1) and Jurong West(asia-southeast1) with 32 vCPUs provisioned compute capacity. The compute cost for the deployment is calculated by multiplying the number of vCPUs provisioned by the highest per vCPU-hour rate amongst Iowa ($0.1000000), St. Ghislain ($0.1130000) and Jurong West ($0.1210000) regions: (32 vCPU \* $0.121), which equals $3.872 per hour. +For example, consider a three-region Multi-Region GCP cluster provisioned in Iowa (us-central1), St. Ghislain (europe-central1) and Jurong West (asia-southeast1) with 32 vCPUs provisioned compute capacity. The compute cost for the cluster is calculated by multiplying the number of vCPUs provisioned by the highest per vCPU-hour rate amongst Iowa ($0.100), St. Ghislain ($0.113) and Jurong West ($0.121) regions: (32 vCPU \* $0.121), which equals $3.872 per hour. **Note:** These prices are intended as examples only. For the latest pricing, refer to [CockroachDB Pricing](https://www.cockroachlabs.com/pricing/). @@ -104,13 +62,33 @@ For example, consider a three region Multi-Region GCP deployment provisioned in
-For an Advanced cluster, each node is provisioned with dedicated vCPU resources. Users can customize the number of vCPUs per node by selecting desired compute per node. This configuration applies to all nodes in the cluster. Compute costs are based on the vCPUs provisioned for each node, with rates depending on the cloud provider and the region. +For an Advanced cluster, each node is provisioned with dedicated compute resources. Users can customize the number of vCPUs per node, which applies to all nodes in the cluster. Compute costs are based on the vCPUs provisioned for each node, with rates depending on the cloud provider, region, and whether a security add-on is enabled. -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. +Compute charges are calculated by multiplying the hourly rate of the provisioned compute by the number of nodes in the cluster. Hourly charges are accumulated throughout the month to determine the total monthly charge. -For example, consider a GCP cluster provisioned in Oregon (us-west1). The cluster consists of three nodes, each with 8vCPU, 32 GiB of RAM. The compute cost for the cluster is determined by multiplying the hourly rate of 8vCPU, 32GiB RAM machine type ($1.0620000) and the total number of nodes (3), which equals $3.1860000 per hour. +For example, consider a GCP cluster provisioned in Oregon (us-west1). The cluster consists of three nodes, each with 8vCPU, 32 GiB of RAM. The compute cost for the cluster is determined by multiplying the hourly rate of 8vCPU, 32GiB RAM machine type ($1.062) and the total number of nodes (3), which equals $3.186 per hour. -**Note:** These prices are intended as examples only. For the latest pricing, refer to [CockroachDB Pricing](https://www.cockroachlabs.com/pricing/). +**Note:** These prices are intended as examples only. For the latest pricing, refer to [CockroachDB Pricing](https://www.cockroachlabs.com/pricing/). + +
+ +### IOPS + +
+ +IOPS are included as part of request units (RUs). + +
+ +
+ +IOPS are included in storage costs. + +
+ +
+ +For Advanced clusters on AWS, each node will incur charges for the provisioned IOPS, an amount determined based on the allocated storage size (in GiB).
@@ -118,27 +96,27 @@ For example, consider a GCP cluster provisioned in Oregon (us-west1). The cluste
-In CockroachDB Basic, storage 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. +For CockroachDB Basic clusters, storage 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 depending on the cloud provider and the region where the cluster is hosted. Basic plan deployments charge storage at $0.50 per GiB-hour. +Storage is billed hourly, with [rates](https://www.cockroachlabs.com/pricing) depending on the cloud provider and the region where the cluster is hosted. Basic plan clusters charge for storage per GiB-hour. These charges are accumulated throughout the month to determine the total monthly storage charges.
-For Standard clusters, storage 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. +For CockroachDB Standard clusters, storage 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) specific to each cloud provider and the region where the cluster is hosted. CockroachDB Cloud measures storage in GiB-hour. These charges are accumulated throughout the month to determine the total monthly storage charges. -A CockroachDB Standard cluster maintains a minimum of three replicas of your data. The second and third replicas are included, with no additional storage charge. If you add further replicas, each will incur a storage cost equal to that of the first replica—the logical database size. +A CockroachDB Standard cluster maintains a minimum of three [replicas](https://www.cockroachlabs.com/docs/stable/architecture/replication-layer) of your data. The second and third replicas are included, with no additional storage charge. If you add further replicas, each will incur a storage cost equal to that of the first replica—the logical database size.
-Each Advanced cluster is provisioned with dedicated storage, and users can configure the storage size for each node when setting up their cluster. This storage setting applies to all nodes in the cluster. The storage is billed hourly, with the rate depending on the cloud provider and the region where the cluster is hosted. Storage costs are independent of other resources, meaning you can adjust your cluster's storage capacity without altering its vCPU or memory configurations. For guidance on provisioning compute and storage, refer to [Plan Your Cluster]({% link cockroachcloud/plan-your-cluster-advanced.md %}). +Each Advanced cluster is provisioned with dedicated storage, and users can configure the per-node storage size when setting up their cluster. This storage setting applies to all nodes in the cluster. The storage is billed hourly, with the rate depending on the cloud provider, the region where the cluster is hosted, and whether the Advanced security add-on is enabled. Storage costs are independent of other resources, meaning you can adjust your cluster's storage capacity without altering its compute capacity. For guidance on provisioning compute and storage, refer to [Plan Your Cluster](https://cockroachlabs.com/docs/cockroachcloud/plan-your-cluster-advanced.html). -- For AWS clusters: Storage charge (per hour) is calculated by multiplying the storage size (in GiB) by the per GiB-hour rate for storage, plus any additional charges for IOPS. +- For AWS clusters: Storage charge (per hour) is calculated by multiplying the storage size (in GiB) by the per GiB-hour rate for storage, plus any additional charges for IOPS. - For GCP and Azure clusters: Node storage charge (per hour) is determined by multiplying the storage size (in GiB) by the per GiB-hour rate, without additional IOPS fees. These charges are accumulated throughout the month to determine the total monthly storage charges. @@ -149,6 +127,42 @@ For example, consider a GCP cluster provisioned in Oregon (us-west1). The cluste
+### Backups + +
+ +Backups on Basic clusters are included in the Request Unit costs. Managed backups occur daily and are not configurable. + +
+ +
+ +[Managed Backups](https://www.cockroachlabs.com/docs/cockroachcloud/managed-backups) are charged per-GiB storage rates that vary per cloud provider, region, and backup [frequency](https://www.cockroachlabs.com/docs/cockroachcloud/managed-backups#frequency) (daily vs. more than daily). The per-GiB unit prices are tiered, based on the amount of backup data stored: Less than 5 GiB-Month, 5 to 100 GiB-Month, 100 to 500 GiB-Month, 500 to 1000 GiB-Month, or 1000 GiB-Month and higher. + +[Self-Managed Backups](https://www.cockroachlabs.com/docs/cockroachcloud/take-and-restore-self-managed-backups) to your own object storage are charged a per-GiB fee for the data transferred. This option provides an advanced backup scheduler and additional control over backup storage placement. + +For further details, refer to CockroachDB Cloud [Pricing](https://www.cockroachlabs.com/pricing/). + +{{site.data.alerts.callout_info}} +Customers will not be charged for backups for CockroachDB {{ site.data.products.standard }} or {{ site.data.products.advanced }} clusters during the current [Preview](#usage-based-billing-metrics-in-preview) of usage-based metrics. +{{site.data.alerts.end}} + +
+ +
+ +[Managed Backups](https://www.cockroachlabs.com/docs/cockroachcloud/managed-backups) are charged per-GiB storage rates that vary per cloud provider, region, and backup [frequency](https://www.cockroachlabs.com/docs/cockroachcloud/managed-backups#frequency) (daily vs. more than daily). The per-GiB unit prices are tiered, based on the amount of backup data stored: Less than 5 GiB-Month, 5 to 100 GiB-Month, 100 to 500 GiB-Month, 500 to 1000 GiB-Month, or 1000 GiB-Month and higher. + +[Self-Managed Backups](https://www.cockroachlabs.com/docs/cockroachcloud/take-and-restore-self-managed-backups) to your own object storage are charged a per-GiB fee for the data transferred. This option provides an advanced backup scheduler and additional control over backup storage placement. + +For further details, refer to CockroachDB Cloud [Pricing](https://www.cockroachlabs.com/pricing/). + +{{site.data.alerts.callout_info}} +Customers will not be charged for backups for CockroachDB {{ site.data.products.standard }} or {{ site.data.products.advanced }} clusters during the current [Preview](#usage-based-billing-metrics-in-preview) of usage-based metrics. +{{site.data.alerts.end}} + +
+ ### Data transfer
@@ -163,17 +177,29 @@ Customers will not be charged for data transfer for CockroachDB {{ site.data.pro For CockroachDB Standard and Advanced, CockroachDB Cloud bills directly to customers based on their usage with a zero-dollar rate during the preview period. -The usage data is based on the volume of data moved (per GiB) and the cloud provider’s line item for each type of data transfer, which CockroachDB categorizes as **Same-region data transfer**, **Cross-Region data transfer**, or **Public Internet data transfer**. +The usage data is based on the volume of data moved (per GiB) and the cloud provider’s identified data transfer type, which CockroachDB categorizes as **Same-region data transfer**, **Cross-Region data transfer**, or **Public Internet data transfer**. Each category is reflected as a line item on your invoice. Cloud providers may vary in how they calculate each category. We recommend consulting the provider’s documentation for details (i.e. [AWS](https://aws.amazon.com/ec2/pricing/on-demand/), [GCP](https://cloud.google.com/vpc/network-pricing), or [Azure](https://azure.microsoft.com/en-us/pricing/details/bandwidth/)). #### Same-region -A minimum production grade CockroachDB Advanced deployment consists of three nodes or more placed across three Availability Zones (AZs) within the selected region. When data moves between these AZs within a single region, this is considered same-region data transfer. +There are no charges for same-region data transfer between CockroachDB cluster nodes. Data egressing the cluster to endpoints in the same region for backups or changefeeds, or using private connectivity, is charged the cloud provider's list price for same-region data transfer. #### Cross-region -Similar to same-region data transfer , when data moves between CockroachDB nodes across multiple regions, we get cross-region charges (also known as inter-region charges). Typically, data transfer costs across regions are higher than data transfer costs across AZs (data centers) in a single region. +When data moves between CockroachDB nodes that are in different regions, or from a CockroachDB node to another endpoint in a different region, it is metered as cross-region data transfer. + +Cross-region data transfer includes: + +- Data transfer required to support queries that involve lookups on nodes in another region. +- CockroachDB replication across nodes that are in different regions. +- Data egress from the CockroachDB Cloud cluster via supported [private connectivity](https://www.cockroachlabs.com/docs/cockroachcloud/connect-to-your-cluster#establish-private-connectivity) services to a private endpoint in another region. +- [Managed backup](https://www.cockroachlabs.com/docs/cockroachcloud/backup-and-restore-overview#managed-backups) and [Self-managed backup](https://www.cockroachlabs.com/docs/cockroachcloud/take-and-restore-self-managed-backups) data transfer to another region. +- Change Data Capture (changefeed) data transfer to another region. + +Customers are charged the cloud service provider’s (CSP) list price for metered cross-region data transfer. + +Typically, data transfer costs across regions are higher than data transfer costs across AZs (data centers) in a single region. #### Public internet @@ -189,17 +215,29 @@ Customers will not be charged for data transfer for CockroachDB {{ site.data.pro For CockroachDB Standard and Advanced, CockroachDB Cloud bills directly to customers based on their usage with a zero-dollar rate during the preview period. -The usage data is based on the volume of data moved (per GiB) and the cloud provider’s line item for each type of data transfer, which CockroachDB categorizes as **Same-region data transfer**, **Cross-Region data transfer**, or **Public Internet data transfer**. +The usage data is based on the volume of data moved (per GiB) and the cloud provider’s identified data transfer type, which CockroachDB categorizes as **Same-region data transfer**, **Cross-Region data transfer**, or **Public Internet data transfer**. Each category is reflected as a line item on your invoice. Cloud providers may vary in how they calculate each category. We recommend consulting the provider’s documentation for details (i.e. [AWS](https://aws.amazon.com/ec2/pricing/on-demand/), [GCP](https://cloud.google.com/vpc/network-pricing), or [Azure](https://azure.microsoft.com/en-us/pricing/details/bandwidth/)). #### Same-region -A minimum production grade CockroachDB Advanced deployment consists of three nodes or more placed across three Availability Zones (AZs) within the selected region. When data moves between these AZs within a single region, this is considered same-region data transfer. +There are no charges for same-region data transfer between CockroachDB cluster nodes. Data egressing the cluster to endpoints in the same region for backups or changefeeds, or using private connectivity, is charged the cloud provider's list price for same-region data transfer. #### Cross-region -Similar to same-region data transfer , when data moves between CockroachDB nodes across multiple regions, we get cross-region charges (also known as inter-region charges). Typically, data transfer costs across regions are higher than data transfer costs across AZs (data centers) in a single region. +When data moves between CockroachDB nodes that are in different regions, or from a CockroachDB node to another endpoint in a different region, it is metered as cross-region data transfer. + +Cross-region data transfer includes: + +- Data transfer required to support queries that involve lookups on nodes in another region. +- CockroachDB replication across nodes that are in different regions. +- Data egress from the CockroachDB Cloud cluster via supported [private connectivity](https://www.cockroachlabs.com/docs/cockroachcloud/connect-to-your-cluster#establish-private-connectivity) services to a private endpoint in another region. +- [Managed backup](https://www.cockroachlabs.com/docs/cockroachcloud/backup-and-restore-overview#managed-backups) and [Self-managed backup](https://www.cockroachlabs.com/docs/cockroachcloud/take-and-restore-self-managed-backups) data transfer to another region. +- Change Data Capture (changefeed) data transfer to another region. + +Customers are charged the cloud service provider’s (CSP) list price for metered cross-region data transfer. + +Typically, data transfer costs across regions are higher than data transfer costs across AZs (data centers) in a single region. #### Public internet @@ -207,7 +245,7 @@ This is the usage for any data leaving CockroachDB such as SQL data being sent t
-### Changefeeds +### Change Data Capture (Changefeeds) All CockroachDB {{ site.data.products.cloud }} clusters can use [Enterprise Changefeeds]({% link {{ site.current_cloud_version}}/how-does-an-enterprise-changefeed-work.md %}). @@ -239,16 +277,12 @@ Customers will not be charged for CockroachDB {{ site.data.products.standard }} ## Usage-based billing metrics in Preview -Metering for usage-based billing of data transfer, managed backup storage, and changefeeds is now in [Preview]({% link {{site.current_cloud_version }}/cockroachdb-feature-availability.md %}) for all CockroachDB Cloud organizations. +Metering for usage-based billing of data transfer, managed backup storage, and changefeeds is in [Preview](https://www.cockroachlabs.com/docs/stable/cockroachdb-feature-availability) for all CockroachDB Cloud organizations. -- [Usage metrics]({% link cockroachcloud/costs.md %}) for data transfer, managed backup storage, and changefeeds are now visible for CockroachDB Standard and Advanced clusters in the CockroachDB Cloud Console. You can view your usage across these metrics on the [Billing page](https://cockroachlabs.cloud/billing/overview) and on invoices. -- There will be no usage-based charges associated with these metrics during the preview period, which is in effect through November 30, 2024. During this time, line items with a charge of $0 will be shown for each metric on your monthly invoice. -- We will share pricing for these usage-based costs by November 1, 2024. -- On December 1, 2024, once the preview has ended, pricing for these metrics goes into effect immediately for new customers and customers billed monthly, and upon contract renewal for customers billed by invoice. - -{{site.data.alerts.callout_info}} -Bytes transferred for [managed backups]({% link cockroachcloud/managed-backups.md %}) on CockroachDB Standard are not yet metered under [Data Transfer]({% link cockroachcloud/costs.md %}#data-transfer) metrics. This will be implemented during the Preview period and be announced in a future release note. -{{site.data.alerts.end}} +- Usage metrics for data transfer, managed backup storage, and changefeeds are now visible for CockroachDB Standard and Advanced clusters in the CockroachDB Cloud Console. You can view your usage across these metrics on the [Billing page](https://cockroachlabs.cloud/billing/overview) and on invoices. +- There will be no usage-based charges associated with these metrics during the Preview period, which is in effect through November 30, 2024. During this time, line items with a charge of $0 will be shown for each metric on your monthly invoice. +- Future pricing for these usage-based costs is available on the [Pricing](https://www.cockroachlabs.com/pricing) page. +- On December 1, 2024, once the Preview has ended, pricing for these metrics goes into effect immediately for new customers and for existing pay-as-you-go customers (e.g. paying monthly by credit card). Customers with annual or multi-year contracts will continue to preview these line items without incurring charges for them (i.e. expending credits) through the end of their current contract term. ## Learn more diff --git a/src/current/releases/cloud.md b/src/current/releases/cloud.md index 72108d6f4d8..f5c22d0b0c8 100644 --- a/src/current/releases/cloud.md +++ b/src/current/releases/cloud.md @@ -15,6 +15,14 @@ Get future release notes emailed to you: {% include marketo.html formId=1083 %} +## November 1, 2024 + +Cockroach Labs has announced [updated pricing](https://www.cockroachlabs.com/blog/improved-cockroachdb-cloud-pricing/) for CockroachDB Cloud. This new pricing model goes into effect December 1, 2024 for new customers and existing pay-as-you-go customers, and upon renewal for annual or multi-year contract customers. + +A [Preview](https://www.cockroachlabs.com/docs/cockroachcloud/costs#usage-based-billing-metrics-in-preview) of metering for usage-based billing of data transfer, backups, and changefeeds remains in effect through November 30, 2024. During this Preview, line items with a charge of $0 will be shown on your monthly invoice for these items. Customers with existing annual or multi-year contracts may continue to preview these line items until charges begin upon contract renewal. + +For more information, refer to [CockroachDB Cloud Costs](https://www.cockroachlabs.com/docs/cockroachcloud/costs) and the [CockroachDB Pricing](https://www.cockroachlabs.com/pricing/) page. + ## October 29, 2024 The new official [Cockroach Labs Okta app integration]({% link cockroachcloud/configure-cloud-org-sso.md %}#add-a-custom-authentication-method) eases the configuration of OIDC and SAML SSO authentication methods for CockroachDB {{ site.data.products.cloud }} organizations. Previously, a custom OIDC or SAML app integration in Okta was required. @@ -31,16 +39,12 @@ The new official [Cockroach Labs Okta app integration]({% link cockroachcloud/co ## October 1, 2024 -Metering for usage-based billing of data transfer, managed backup storage, and changefeeds is now in [Preview]({% link {{site.current_cloud_version }}/cockroachdb-feature-availability.md %}) for all CockroachDB Cloud organizations. +[Metering](https://www.cockroachlabs.com/docs/cockroachcloud/costs) for usage-based billing of data transfer, managed backup storage, and changefeeds is now in [Preview](https://www.cockroachlabs.com/docs/stable/cockroachdb-feature-availability#features-in-preview) for all CockroachDB Cloud organizations. -- [Usage metrics]({% link cockroachcloud/costs.md %}) for data transfer, managed backup storage, and changefeeds are now visible for CockroachDB Standard and Advanced clusters in the CockroachDB Cloud Console. You can view your usage across these metrics on the [Billing page](https://cockroachlabs.cloud/billing/overview) and on invoices. -- There will be no usage-based charges associated with these metrics during the preview period, which is in effect through November 30, 2024. During this time, line items with a charge of $0 will be shown for each metric on your monthly invoice. -- We will share pricing for these usage-based costs by November 1, 2024. -- On December 1, 2024, once the preview has ended, pricing for these metrics goes into effect immediately for new customers and customers billed monthly, and upon contract renewal for customers billed by invoice. - -{{site.data.alerts.callout_info}} -Bytes transferred for [managed backups]({% link cockroachcloud/managed-backups.md %}) on CockroachDB Standard are not yet metered under [Data Transfer]({% link cockroachcloud/costs.md %}#data-transfer) metrics. This will be implemented during the Preview period and be announced in a future release note. -{{site.data.alerts.end}} +- Usage metrics for data transfer, managed backup storage, and changefeeds are now visible for CockroachDB Standard and Advanced clusters in the CockroachDB Cloud Console. You can view your usage across these metrics on the [Billing page](https://cockroachlabs.cloud/billing/overview) and on invoices. +- There will be no usage-based charges associated with these metrics during the Preview period, which is in effect through November 30, 2024\. During this time, line items with a charge of $0 will be shown for each metric on your monthly invoice. +- We will share pricing for these usage-based costs by November 1, 2024\. +- On December 1, 2024, once the Preview has ended, pricing for these metrics goes into effect immediately for new customers and for existing pay-as-you-go customers (e.g. paying monthly by credit card). Customers with annual or multi-year contracts will continue to preview these line items without incurring charges for them (i.e. expending credits) through the end of their current contract term. ## September 25, 2024 diff --git a/src/current/v23.1/performance-benchmarking-with-tpcc-medium.md b/src/current/v23.1/performance-benchmarking-with-tpcc-medium.md index 73947b42a6d..5b8f39219f5 100644 --- a/src/current/v23.1/performance-benchmarking-with-tpcc-medium.md +++ b/src/current/v23.1/performance-benchmarking-with-tpcc-medium.md @@ -134,7 +134,6 @@ You'll be importing a large TPC-C data set. To speed that up, you can tweak some {% include_cached copy-clipboard.html %} ~~~ sql > SET CLUSTER SETTING rocksdb.ingest_backpressure.l0_file_count_threshold = 100; - SET CLUSTER SETTING rocksdb.ingest_backpressure.pending_compaction_threshold = '5 GiB'; SET CLUSTER SETTING schemachanger.backfiller.max_buffer_size = '5 GiB'; SET CLUSTER SETTING kv.snapshot_rebalance.max_rate = '128 MiB'; SET CLUSTER SETTING rocksdb.min_wal_sync_interval = '500us'; diff --git a/src/current/v23.2/cockroachdb-feature-availability.md b/src/current/v23.2/cockroachdb-feature-availability.md index a06692f2fb2..547e23a36bd 100644 --- a/src/current/v23.2/cockroachdb-feature-availability.md +++ b/src/current/v23.2/cockroachdb-feature-availability.md @@ -39,6 +39,14 @@ Any feature made available in a phase prior to GA is provided without any warran ## Features in preview +### Usage-based billing metrics + +Metering for [usage-based billing](https://www.cockroachlabs.com/docs/cockroachcloud/costs) of data transfer, managed backup storage, and changefeeds is in Preview for all CockroachDB Standard and Advanced clusters through November 2024\. You can view your usage in the CockroachDB Cloud Console, where line items with a charge of $0 are shown for each metric. There will be no usage-based charges associated with these metrics during the Preview period. + +On December 1, 2024, once the Preview has ended, pricing for these metrics goes into effect immediately for new customers and for existing pay-as-you-go customers (e.g. paying monthly by credit card). Customers with annual or multi-year contracts will continue to preview these line items without incurring charges for them (i.e. expending credits) through the end of their current contract term. + +For more information, refer to [CockroachDB Cloud Costs: Usage-based billing metrics in Preview](https://www.cockroachlabs.com/docs/cockroachcloud/costs#usage-based-billing-metrics-in-preview) and the announcements in the release notes published [October 1](https://www.cockroachlabs.com/docs/releases/cloud#october-1-2024) and [November 1](https://www.cockroachlabs.com/docs/releases/cloud#november-1-2024). + {{site.data.alerts.callout_info}} **The following features are in preview** and are subject to change. To share feedback and/or issues, contact [Support](https://support.cockroachlabs.com/hc). {{site.data.alerts.end}} diff --git a/src/current/v23.2/performance-benchmarking-with-tpcc-medium.md b/src/current/v23.2/performance-benchmarking-with-tpcc-medium.md index 73947b42a6d..5b8f39219f5 100644 --- a/src/current/v23.2/performance-benchmarking-with-tpcc-medium.md +++ b/src/current/v23.2/performance-benchmarking-with-tpcc-medium.md @@ -134,7 +134,6 @@ You'll be importing a large TPC-C data set. To speed that up, you can tweak some {% include_cached copy-clipboard.html %} ~~~ sql > SET CLUSTER SETTING rocksdb.ingest_backpressure.l0_file_count_threshold = 100; - SET CLUSTER SETTING rocksdb.ingest_backpressure.pending_compaction_threshold = '5 GiB'; SET CLUSTER SETTING schemachanger.backfiller.max_buffer_size = '5 GiB'; SET CLUSTER SETTING kv.snapshot_rebalance.max_rate = '128 MiB'; SET CLUSTER SETTING rocksdb.min_wal_sync_interval = '500us'; diff --git a/src/current/v24.1/cockroachdb-feature-availability.md b/src/current/v24.1/cockroachdb-feature-availability.md index 8789076f2a2..b5f70ff2441 100644 --- a/src/current/v24.1/cockroachdb-feature-availability.md +++ b/src/current/v24.1/cockroachdb-feature-availability.md @@ -43,6 +43,14 @@ Any feature made available in a phase prior to GA is provided without any warran **The following features are in preview** and are subject to change. To share feedback and/or issues, contact [Support](https://support.cockroachlabs.com/hc). {{site.data.alerts.end}} +### Usage-based billing metrics + +Metering for [usage-based billing](https://www.cockroachlabs.com/docs/cockroachcloud/costs) of data transfer, managed backup storage, and changefeeds is in Preview for all CockroachDB Standard and Advanced clusters through November 2024\. You can view your usage in the CockroachDB Cloud Console, where line items with a charge of $0 are shown for each metric. There will be no usage-based charges associated with these metrics during the Preview period. + +On December 1, 2024, once the Preview has ended, pricing for these metrics goes into effect immediately for new customers and for existing pay-as-you-go customers (e.g. paying monthly by credit card). Customers with annual or multi-year contracts will continue to preview these line items without incurring charges for them (i.e. expending credits) through the end of their current contract term. + +For more information, refer to [CockroachDB Cloud Costs: Usage-based billing metrics in Preview](https://www.cockroachlabs.com/docs/cockroachcloud/costs#usage-based-billing-metrics-in-preview) and the announcements in the release notes published [October 1](https://www.cockroachlabs.com/docs/releases/cloud#october-1-2024) and [November 1](https://www.cockroachlabs.com/docs/releases/cloud#november-1-2024). + ### CockroachDB Cloud Folders [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. diff --git a/src/current/v24.1/performance-benchmarking-with-tpcc-medium.md b/src/current/v24.1/performance-benchmarking-with-tpcc-medium.md index 73947b42a6d..5b8f39219f5 100644 --- a/src/current/v24.1/performance-benchmarking-with-tpcc-medium.md +++ b/src/current/v24.1/performance-benchmarking-with-tpcc-medium.md @@ -134,7 +134,6 @@ You'll be importing a large TPC-C data set. To speed that up, you can tweak some {% include_cached copy-clipboard.html %} ~~~ sql > SET CLUSTER SETTING rocksdb.ingest_backpressure.l0_file_count_threshold = 100; - SET CLUSTER SETTING rocksdb.ingest_backpressure.pending_compaction_threshold = '5 GiB'; SET CLUSTER SETTING schemachanger.backfiller.max_buffer_size = '5 GiB'; SET CLUSTER SETTING kv.snapshot_rebalance.max_rate = '128 MiB'; SET CLUSTER SETTING rocksdb.min_wal_sync_interval = '500us'; diff --git a/src/current/v24.2/cockroachdb-feature-availability.md b/src/current/v24.2/cockroachdb-feature-availability.md index 4a601e3912c..cd7ba232ab8 100644 --- a/src/current/v24.2/cockroachdb-feature-availability.md +++ b/src/current/v24.2/cockroachdb-feature-availability.md @@ -49,7 +49,11 @@ Any feature made available in a phase prior to GA is provided without any warran ### Usage-based billing metrics -Metering for [usage-based billing]({% link cockroachcloud/costs.md %}) of data transfer, managed backup storage, and changefeeds is now in Preview for all CockroachDB Standard and Advanced clusters through November 2024. You can view your usage in the CockroachDB Cloud Console, where line items with a charge of $0 will be shown for each metric. There will be no usage-based charges associated with these metrics during the preview period. For more information, refer to [CockroachDB Cloud Costs: Usage-based billing metrics in Preview]({% link cockroachcloud/costs.md %}#usage-based-billing-metrics-in-preview) or the [announcement]({% link releases/cloud.md %}#october-1-2024) in the release notes. +Metering for [usage-based billing](https://www.cockroachlabs.com/docs/cockroachcloud/costs) of data transfer, managed backup storage, and changefeeds is in Preview for all CockroachDB Standard and Advanced clusters through November 2024\. You can view your usage in the CockroachDB Cloud Console, where line items with a charge of $0 are shown for each metric. There will be no usage-based charges associated with these metrics during the Preview period. + +On December 1, 2024, once the Preview has ended, pricing for these metrics goes into effect immediately for new customers and for existing pay-as-you-go customers (e.g. paying monthly by credit card). Customers with annual or multi-year contracts will continue to preview these line items without incurring charges for them (i.e. expending credits) through the end of their current contract term. + +For more information, refer to [CockroachDB Cloud Costs: Usage-based billing metrics in Preview](https://www.cockroachlabs.com/docs/cockroachcloud/costs#usage-based-billing-metrics-in-preview) and the announcements in the release notes published [October 1](https://www.cockroachlabs.com/docs/releases/cloud#october-1-2024) and [November 1](https://www.cockroachlabs.com/docs/releases/cloud#november-1-2024). ### CockroachDB Standard diff --git a/src/current/v24.2/performance-benchmarking-with-tpcc-medium.md b/src/current/v24.2/performance-benchmarking-with-tpcc-medium.md index 73947b42a6d..5b8f39219f5 100644 --- a/src/current/v24.2/performance-benchmarking-with-tpcc-medium.md +++ b/src/current/v24.2/performance-benchmarking-with-tpcc-medium.md @@ -134,7 +134,6 @@ You'll be importing a large TPC-C data set. To speed that up, you can tweak some {% include_cached copy-clipboard.html %} ~~~ sql > SET CLUSTER SETTING rocksdb.ingest_backpressure.l0_file_count_threshold = 100; - SET CLUSTER SETTING rocksdb.ingest_backpressure.pending_compaction_threshold = '5 GiB'; SET CLUSTER SETTING schemachanger.backfiller.max_buffer_size = '5 GiB'; SET CLUSTER SETTING kv.snapshot_rebalance.max_rate = '128 MiB'; SET CLUSTER SETTING rocksdb.min_wal_sync_interval = '500us'; diff --git a/src/current/v24.3/performance-benchmarking-with-tpcc-medium.md b/src/current/v24.3/performance-benchmarking-with-tpcc-medium.md index 73947b42a6d..5b8f39219f5 100644 --- a/src/current/v24.3/performance-benchmarking-with-tpcc-medium.md +++ b/src/current/v24.3/performance-benchmarking-with-tpcc-medium.md @@ -134,7 +134,6 @@ You'll be importing a large TPC-C data set. To speed that up, you can tweak some {% include_cached copy-clipboard.html %} ~~~ sql > SET CLUSTER SETTING rocksdb.ingest_backpressure.l0_file_count_threshold = 100; - SET CLUSTER SETTING rocksdb.ingest_backpressure.pending_compaction_threshold = '5 GiB'; SET CLUSTER SETTING schemachanger.backfiller.max_buffer_size = '5 GiB'; SET CLUSTER SETTING kv.snapshot_rebalance.max_rate = '128 MiB'; SET CLUSTER SETTING rocksdb.min_wal_sync_interval = '500us';