Skip to content

Commit 9913553

Browse files
author
github-actions
committed
update MD by dispatch event pingcap/docs release-cloud
1 parent a8cf4d4 commit 9913553

File tree

1 file changed

+117
-2
lines changed

1 file changed

+117
-2
lines changed

‎markdown-pages/en/tidbcloud/master/tidb-cloud/tidb-cloud-billing.md‎

Lines changed: 117 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,124 @@ summary: Learn about TiDB Cloud billing.
77

88
> **Note:**
99
>
10-
> [TiDB Cloud Starter clusters](/tidb-cloud/select-cluster-tier.md#tidb-cloud-starter) are free until April 30, 2025, with a 100% discount off. After that, usage beyond the [free quota](/tidb-cloud/select-cluster-tier.md#usage-quota) will be charged.
10+
> [TiDB Cloud Starter clusters](/tidb-cloud/select-cluster-tier.md#tidb-cloud-starter) are free until June 9, 2025, with a 100% discount off. After that, usage beyond the [free quota](/tidb-cloud/select-cluster-tier.md#usage-quota) will be charged.
11+
12+
TiDB Cloud charges according to the resources that you consume.
13+
14+
## Pricing
15+
16+
TiDB Cloud offers the following two pricing options to suit different needs:
17+
18+
* TiDB Cloud Starter: you are charged based on the number of Request Units (RUs) consumed by your application.
19+
* TiDB Cloud Essential: you are charged based on the number of provisioned Request Capacity Units (RCUs), **not** on the actual usage by your application.
20+
21+
### Request Unit (RU) and Request Capacity Unit (RCU)
22+
23+
A **Request Unit (RU)** is a unit of measure used to represent the amount of resources consumed by a single request to the database. The amount of RUs consumed by a request depends on various factors, such as the operation type or the amount of data being retrieved or modified.
24+
25+
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.
26+
27+
Currently, the RU includes statistics for the following resources:
28+
29+
<table><thead>
30+
<tr>
31+
<th>Resource</th>
32+
<th>RU Consumption</th>
33+
</tr></thead>
34+
<tbody>
35+
<tr>
36+
<td rowspan="3">Read</td>
37+
<td>2 storage read batches consume 1 RU</td>
38+
</tr>
39+
<tr>
40+
<td>8 storage read requests consume 1 RU</td>
41+
</tr>
42+
<tr>
43+
<td>64 KiB read request payload consumes 1 RU</td>
44+
</tr>
45+
<tr>
46+
<td rowspan="4">Write*</td>
47+
<td>2 storage write batches consume 1 RU</td>
48+
</tr>
49+
<tr>
50+
<td>2 storage write requests consume 1 RU</td>
51+
</tr>
52+
<tr>
53+
<td>2 KiB write request payload consumes 1 RU</td>
54+
</tr>
55+
<tr>
56+
<td>16 KiB write request payload consumes 1 RU (for transactions** &gt;= 16MiB)</td>
57+
</tr>
58+
<tr>
59+
<td>SQL CPU</td>
60+
<td>3 ms consumes 1 RU</td>
61+
</tr>
62+
<tr>
63+
<td rowspan="2">Network Egress</td>
64+
<td>1 KiB read consumes 1 RU for public endpoint</td>
65+
</tr>
66+
<tr>
67+
<td>4 KiB read consumes 1 RU for private endpoint</td>
68+
</tr>
69+
</tbody>
70+
</table>
1171

12-
TiDB Cloud charges according to the resources that you consume. You can visit the [TiDB Cloud Starter Pricing Details](https://www.pingcap.com/tidb-serverless-pricing-details/) pages to get more information about the pricing.
72+
> **Note:**
73+
>
74+
> - 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.
75+
> - Transaction**: This applies only to optimistic transactions or autocommit.
76+
77+
### Pricing for TiDB Cloud Starter
78+
79+
See the detailed pricing for each available Alibaba Cloud region below.
80+
81+
| Resource | Singapore |
82+
|----------|-----------|
83+
| Compute (per 1 million RUs) | $0.1 |
84+
| Row-based storage (per GiB/month) | $0.36 |
85+
| Columnar storage (per GiB/month) | $0.09 |
86+
87+
#### Free quota
88+
89+
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.
90+
91+
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.
92+
93+
In total, each organization can get 25 GiB of row-based storage, 25 GiB of columnar storage, and 250 million Request Units (RUs) for free per month. Customers can take advantage of this offer and optimize their operations without worrying about initial costs.
94+
95+
#### Monthly Spending Limit
96+
97+
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.
98+
99+
> **Note:**
100+
>
101+
> You cannot set a spending limit lower than the amount already spent in the current month.
102+
103+
#### Throttling
104+
105+
A cluster will not be throttled unless the spending limit is reached. Once the spending limit is reached, the cluster immediately denies any new connection attempts until the quota is increased or the usage is reset at the start of a new month. Existing connections established before reaching the quota will remain active but will experience throttling.
106+
107+
If the free quota of a cluster is exhausted within the month, the cluster is automatically throttled. This limit will remain in place until you [upgrade it to a scalable cluster](/tidb-cloud/manage-serverless-spend-limit.md#update-spending-limit) or until the next month.
108+
109+
In this way, customers can ensure basic business continuity without paying additional fees. At the same time, customers can adjust the spending limit according to their needs to control their usage and costs.
110+
111+
### Pricing for TiDB Cloud Essential
112+
113+
See the detailed pricing for each available Alibaba Cloud region below.
114+
115+
| Resource | Singapore |
116+
|----------|-----------|
117+
| Compute (per RCU/month) | $0.24 |
118+
| Row-based storage (per GiB/month) | $0.36 |
119+
| Columnar storage (per GiB/month) | $0.09 |
120+
121+
#### Throttling
122+
123+
For TiDB Cloud Essential clusters, the throttling policy is based on the provisioned Request Capacity Units (RCUs). When the workload exceeds the maximum RCU capacity, the cluster will automatically throttle incoming requests to maintain stability. Existing connections will experience throttling, but new connection attempts will be accepted as long as they don't exceed the maximum RCU limit. This ensures predictable performance while protecting the cluster from overload.
124+
125+
### Billing cycle
126+
127+
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.
13128

14129
## Invoices
15130

0 commit comments

Comments
 (0)