Alicloud pricing #21124
Alicloud pricing #21124
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
ti-chi-bot
bot
added
missing-translation-status
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hello @likidu, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
Summary of Changes
Hello! gemini-code-assist here, providing a summary of this pull request. This PR, authored by likidu, focuses on enhancing the documentation for TiDB Cloud billing. The primary goal is to add comprehensive pricing details specifically for Alibaba Cloud regions for both TiDB Cloud Starter and Essential tiers. It also includes updates to the free trial end date and clarifies concepts like Request Units (RU) and Request Capacity Units (RCU), along with details on free quotas, spending limits, throttling, and the billing cycle.
Highlights
- Alibaba Cloud Pricing Added: Detailed pricing tables for TiDB Cloud Starter and Essential tiers are introduced for Alibaba Cloud regions (Singapore, Japan, Mexico).
- RU and RCU Defined: Clear definitions and explanations are provided for Request Units (RU) and Request Capacity Units (RCU), which are key metrics for billing in TiDB Cloud.
- Free Quota and Spending Limit Details: The documentation now includes specifics on the free quota available for Starter clusters and how the Monthly Spending Limit works.
- Throttling Policies Explained: Information on how throttling is applied to both Starter (based on spending limit/free quota) and Essential (based on RCU capacity) clusters is added.
- Free Trial End Date Updated: The free trial end date for TiDB Cloud Starter clusters has been updated from April 30, 2025, to June 9, 2025.
Changelog
Click here to see the changelog
- tidb-cloud/tidb-cloud-billing.md
- Updated the free trial end date for Starter clusters to June 9, 2025.
- Added a new 'Pricing' section covering both Starter and Essential tiers.
- Included definitions for Request Unit (RU) and Request Capacity Unit (RCU).
- Provided a table detailing RU consumption for various resources.
- Added pricing tables for Alibaba Cloud regions (Singapore, Japan, Mexico) for Starter clusters (per 1M RUs, row/column storage).
- Detailed the Free Quota policy for Starter clusters (per cluster and per organization).
- Explained the Monthly Spending Limit feature for Starter clusters.
- Described the throttling behavior for Starter clusters.
- Added pricing tables for Alibaba Cloud regions (Singapore, Japan, Mexico) for Essential clusters (per RCU, row/column storage).
- Described the throttling behavior for Essential clusters.
- Added a section explaining the billing cycle.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Code Review
The pull request adds pricing information for TiDB Cloud Starter and Essential on Alibaba Cloud. The changes are well-structured and provide a good overview of the pricing models. However, there are a few areas where clarity and consistency can be improved. I have added comments to address these points.
Summary of Findings
- Clarity and Consistency: Several areas could benefit from improved clarity and consistency in phrasing and formatting.
- Footnotes: The asterisk (*) next to 'Write' needs a footnote to explain its significance. Also, the double asterisk (**) next to 'transactions' needs a footnote to explain its significance.
Merge Readiness
The pull request is almost ready for merging. Addressing the comments above will improve the clarity and consistency of the documentation. I am unable to directly approve this pull request, and recommend that others review and approve this code before merging.
lilin90
added
area/tidb-cloud
ti-chi-bot
bot
removed
the
missing-translation-status
tidb-cloud/tidb-cloud-billing.md
Outdated
| | Write* | 2 storage write batch consumes 1 RU | | ||
| | | 2 storage write request consumes 1 RU | | ||
| | | 1 KiB write request payload consumes 1 RU | | ||
| | | 8 KiB write request payload consumes 1 RU (for transactions** >= 16MiB) | |
There was a problem hiding this comment.
-
Do we also need to add explanations for
Writer*andtransactions**below this table, like that on https://www.pingcap.com/tidb-serverless-pricing-details/?-
*Write: Each write operation is duplicated to multiple storage processes (3 for row-based storage without index), and each duplicate is considered a distinct write operation.
-
**Transaction: This applies only to optimistic transaction or autocommit.
-
-
I can convert this table into a HTML table, so the left column can show like that on https://www.pingcap.com/tidb-serverless-pricing-details/ to avoid confusion.
tidb-cloud/tidb-cloud-billing.md
Outdated
| | | 64 KiB read request payload consumes 1 RU | | ||
| | Write* | 2 storage write batch consumes 1 RU | | ||
| | | 2 storage write request consumes 1 RU | | ||
| | | 1 KiB write request payload consumes 1 RU | |
There was a problem hiding this comment.
| | | 1 KiB write request payload consumes 1 RU | | |
| | | 2 KiB write request payload consumes 1 RU | |
tidb-cloud/tidb-cloud-billing.md
Outdated
| | Write* | 2 storage write batch consumes 1 RU | | ||
| | | 2 storage write request consumes 1 RU | | ||
| | | 1 KiB write request payload consumes 1 RU | | ||
| | | 8 KiB write request payload consumes 1 RU (for transactions** >= 16MiB) | |
There was a problem hiding this comment.
| | | 8 KiB write request payload consumes 1 RU (for transactions** >= 16MiB) | | |
| | | 16 KiB write request payload consumes 1 RU (for transactions** >= 16MiB) | |
tidb-cloud/tidb-cloud-billing.md
Outdated
| | | 1 KiB write request payload consumes 1 RU | | ||
| | | 8 KiB write request payload consumes 1 RU (for transactions** >= 16MiB) | | ||
| | SQL CPU | 3 ms consumes 1 RU | | ||
| | Network Egress | 1 KiB read consumes 1 RU | |
There was a problem hiding this comment.
| | Network Egress | 1 KiB read consumes 1 RU | | |
| | Network Egress | 1 KiB read consumes 1 RU for Public Endpoint | | |
| | | 4 KiB read consumes 1 RU for Private Endpoint | |
Co-authored-by: Lilian Lee <[email protected]>
Co-authored-by: Lilian Lee <[email protected]>
Co-authored-by: Lilian Lee <[email protected]>
Co-authored-by: Lilian Lee <[email protected]>
Co-authored-by: Lilian Lee <[email protected]>
Co-authored-by: Lilian Lee <[email protected]>
| TiDB Cloud offers the following two pricing options to suit different needs: | ||
|
|
||
| * TiDB Cloud Starter: you are charged based on the number of Request Units (RUs) consumed by your application. | ||
| * TiDB Cloud Essential: you are charged based on the number of Request Capacity Units (RCUs) have provisioned, **not** on the actual usage by your application. |
There was a problem hiding this comment.
| * TiDB Cloud Essential: you are charged based on the number of Request Capacity Units (RCUs) have provisioned, **not** on the actual usage by your application. | |
| * TiDB Cloud Essential: you are charged based on the number of provisioned Request Capacity Units (RCUs), **not** on the actual usage by your application. |
|
|
||
| A **Request Capacity Unit (RCU)** is a unit of measure used to represent the provisioned compute capacity for your TiDB Cloud Essential cluster. One RCU provides a fixed amount of compute resources that can process a certain number of RUs per second. The number of RCUs you provision determines your cluster's baseline performance and throughput capacity. | ||
|
|
||
| Currently, the RU will include statistics for the following resources: |
There was a problem hiding this comment.
| Currently, the RU will include statistics for the following resources: | |
| Currently, the RU includes statistics for the following resources: |
| | Write* | 2 storage write batch consumes 1 RU | | ||
| | | 2 storage write request consumes 1 RU | |
There was a problem hiding this comment.
| | Write* | 2 storage write batch consumes 1 RU | | |
| | | 2 storage write request consumes 1 RU | | |
| | Write* | 2 storage write batches consume 1 RU | | |
| | | 2 storage write requests consume 1 RU | |
|
|
||
| > *Write: Each write operation is duplicated to multiple storage processes (3 for row-based storage without index), and each duplicate is considered a distinct write operation. | ||
|
|
||
| > **Transaction: This applies only to optimistic transaction or autocommit. |
There was a problem hiding this comment.
| > **Transaction: This applies only to optimistic transaction or autocommit. | |
| > Transaction**: This applies only to optimistic transactions or autocommit. |
|
|
||
| #### Free quota | ||
|
|
||
| We are offering a free quota up to the first 5 clusters created in each Organization. If you need to create more clusters, you will be required to provide a credit card and set a Monthly Spending Limit. But if you delete some of your previous clusters before creating the 6th, the new cluster will still have a free quota. In other words, you can enjoy the free quota for up to 5 clusters. |
There was a problem hiding this comment.
| We are offering a free quota up to the first 5 clusters created in each Organization. If you need to create more clusters, you will be required to provide a credit card and set a Monthly Spending Limit. But if you delete some of your previous clusters before creating the 6th, the new cluster will still have a free quota. In other words, you can enjoy the free quota for up to 5 clusters. | |
| TiDB Cloud offers a free quota up to the first 5 clusters created in each [organization](/tidb-cloud/manage-user-access.md#organizations). To create more clusters, you will be required to provide a credit card and set a [Monthly Spending Limit](#monthly-spending-limit). But if you delete some of your previous clusters before creating the 6th, the new cluster will still have a free quota. In other words, you can enjoy the free quota for up to 5 clusters. |
| | Row-based storage (per GiB / month) | $0.36 | | ||
| | Columnar-based storage (per GiB / month) | $0.09 | |
There was a problem hiding this comment.
| | Row-based storage (per GiB / month) | $0.36 | | |
| | Columnar-based storage (per GiB / month) | $0.09 | | |
| | Row-based storage (per GiB/month) | $0.36 | | |
| | Columnar storage (per GiB/month) | $0.09 | |
|
|
||
| #### Monthly Spending Limit | ||
|
|
||
| The "Monthly Spending Limit" refers to the maximum amount of money that you are willing to spend on a particular workload in a month. It is a cost-control mechanism that enables you to set a budget for your TiDB Starter clusters. The Monthly Spending Limit must be set to a minimum of $0.01. |
There was a problem hiding this comment.
| The "Monthly Spending Limit" refers to the maximum amount of money that you are willing to spend on a particular workload in a month. It is a cost-control mechanism that enables you to set a budget for your TiDB Starter clusters. The Monthly Spending Limit must be set to a minimum of $0.01. | |
| The Monthly Spending Limit refers to the maximum amount of money that you are willing to spend on a particular workload in a month. It is a cost-control mechanism that enables you to set a budget for your TiDB Cloud Starter clusters. The Monthly Spending Limit must be set to at least $0.01. |
|
|
||
| The "Monthly Spending Limit" refers to the maximum amount of money that you are willing to spend on a particular workload in a month. It is a cost-control mechanism that enables you to set a budget for your TiDB Starter clusters. The Monthly Spending Limit must be set to a minimum of $0.01. | ||
|
|
||
| Note: It is impossible to set a spending limit value lower than the amount already spent for the current month. |
There was a problem hiding this comment.
| Note: It is impossible to set a spending limit value lower than the amount already spent for the current month. | |
| > **Note:** | |
| > | |
| > You cannot set a spending limit lower than the amount already spent in the current month. |
| | Compute (per RCU / month) | $0.24 | | ||
| | Row-based storage (per GiB / month) | $0.36 | | ||
| | Columnar-based storage (per GiB / month) | $0.09 | |
There was a problem hiding this comment.
| | Compute (per RCU / month) | $0.24 | | |
| | Row-based storage (per GiB / month) | $0.36 | | |
| | Columnar-based storage (per GiB / month) | $0.09 | | |
| | Compute (per RCU/month) | $0.24 | | |
| | Row-based storage (per GiB/month) | $0.36 | | |
| | Columnar storage (per GiB/month) | $0.09 | |
|
|
||
| ### Billing cycle | ||
|
|
||
| Each TiDB Cloud bill, corresponding to the previous month's usage, is finalized at the start of every new month. This finalized bill is then charged to your default payment method, typically occurring between the 3rd and 9th day of the respective month. If your usage within the current month reaches or exceeds $500, an automatic charge will be initiated. Please note that the billing cycle operates strictly in accordance with the UTC (+00:00) time zone. |
There was a problem hiding this comment.
| Each TiDB Cloud bill, corresponding to the previous month's usage, is finalized at the start of every new month. This finalized bill is then charged to your default payment method, typically occurring between the 3rd and 9th day of the respective month. If your usage within the current month reaches or exceeds $500, an automatic charge will be initiated. Please note that the billing cycle operates strictly in accordance with the UTC (+00:00) time zone. | |
| Each TiDB Cloud bill, corresponding to the previous month's usage, is finalized at the start of every new month. This finalized bill is charged to your default payment method, typically occurring between the 3rd and 9th day of the respective month. If your usage within the current month reaches or exceeds $500, an automatic charge will be initiated. Note that the billing cycle operates strictly in accordance with the UTC (+00:00) time zone. |
| | Network Egress | 1 KiB read consumes 1 RU for Public Endpoint | | ||
| | | 4 KiB read consumes 1 RU for Private Endpoint | |
There was a problem hiding this comment.
| | Network Egress | 1 KiB read consumes 1 RU for Public Endpoint | | |
| | | 4 KiB read consumes 1 RU for Private Endpoint | | |
| | Network Egress | 1 KiB read consumes 1 RU for public endpoint | | |
| | | 4 KiB read consumes 1 RU for private endpoint | |
|
|
||
| We are offering a free quota up to the first 5 clusters created in each Organization. If you need to create more clusters, you will be required to provide a credit card and set a Monthly Spending Limit. But if you delete some of your previous clusters before creating the 6th, the new cluster will still have a free quota. In other words, you can enjoy the free quota for up to 5 clusters. | ||
|
|
||
| Free Quota will be issued monthly to serverless clusters that meet these qualifications. With the free quota, customers can store 5 GiB of row-based data, 5 GiB of columnar data, and consume 50 million RUs for one month. |
There was a problem hiding this comment.
| Free Quota will be issued monthly to serverless clusters that meet these qualifications. With the free quota, customers can store 5 GiB of row-based data, 5 GiB of columnar data, and consume 50 million RUs for one month. | |
| Free quota is issued monthly to TiDB Cloud Starter clusters that meet these qualifications. With the free quota, each TiDB Cloud Starter cluster can store 5 GiB of row-based data, 5 GiB of columnar data, and consume up to 50 million RUs per month. |
[LGTM Timeline notifier]Timeline:
|
First-time contributors' checklist
What is changed, added or deleted? (Required)
Adding the pricing section for TiDB Cloud Starter and Essential for Alibaba Cloud.
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?