Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

delete 2 vCPU description. #14715

Merged
merged 3 commits into from
Sep 19, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions tidb-cloud/scale-tidb-cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,10 +20,9 @@ For information about how to determine the size of your TiDB cluster, see [Deter

> **Note:**
>
> If the vCPU and RAM size of TiDB or TiKV is set as **2 vCPU, 8 GiB (Beta)** or **4 vCPU, 16 GiB**, note the following restrictions. To bypass these restrictions, you can [increase the vCPU and RAM](#change-vcpu-and-ram) first.
> If the vCPU and RAM size of TiDB or TiKV is set as **4 vCPU, 16 GiB**, note the following restrictions. To bypass these restrictions, you can [increase the vCPU and RAM](#change-vcpu-and-ram) first.
>
> - The node number of TiDB can only be set to 1 or 2, and the node number of TiKV is fixed to 3.
> - 2 vCPU TiDB can only be used with 2 vCPU TiKV, and 2 vCPU TiKV can only be used with 2 vCPU TiDB.
> - 4 vCPU TiDB can only be used with 4 vCPU TiKV, and 4 vCPU TiKV can only be used with 4 vCPU TiDB.
> - TiFlash is unavailable.

Expand Down Expand Up @@ -98,4 +97,4 @@ To change the storage of TiKV or TiFlash, take the following steps:
4. On the **Modify Cluster** page, change the storage of each TiKV or TiFlash node.
5. Review the cluster size in the right pane, and then click **Confirm**.

You can also change the storage of a TiKV or TiFlash node using TiDB Cloud API through the [Modify a TiDB Dedicated cluster](https://docs.pingcap.com/tidbcloud/api/v1beta#tag/Cluster/operation/UpdateCluster) endpoint. Currently, TiDB Cloud API is still in beta. For more information, see [TiDB Cloud API Documentation](https://docs.pingcap.com/tidbcloud/api/v1beta).
You can also change the storage of a TiKV or TiFlash node using TiDB Cloud API through the [Modify a TiDB Dedicated cluster](https://docs.pingcap.com/tidbcloud/api/v1beta#tag/Cluster/operation/UpdateCluster) endpoint. Currently, TiDB Cloud API is still in beta. For more information, see [TiDB Cloud API Documentation](https://docs.pingcap.com/tidbcloud/api/v1beta).
13 changes: 5 additions & 8 deletions tidb-cloud/size-your-cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,17 +23,16 @@ To learn performance test results of different cluster scales, see [TiDB Cloud P

The supported vCPU and RAM sizes include the following:

- 2 vCPU, 8 GiB (Beta)
- 4 vCPU, 16 GiB
- 8 vCPU, 16 GiB
- 16 vCPU, 32 GiB

> **Note:**
>
> If the vCPU and RAM size of TiDB is set as **2 vCPU, 8 GiB (Beta)** or **4 vCPU, 16 GiB**, note the following restrictions:
> If the vCPU and RAM size of TiDB is set as **4 vCPU, 16 GiB**, note the following restrictions:
>
> - The node number of TiDB can only be set to 1 or 2, and the node number of TiKV is fixed to 3.
> - 2 vCPU TiDB can only be used with 2 vCPU TiKV. 4 vCPU TiDB can only be used with 4 vCPU TiKV.
> - 4 vCPU TiDB can only be used with 4 vCPU TiKV.
> - TiFlash is unavailable.

### TiDB node number
Expand Down Expand Up @@ -85,18 +84,17 @@ To learn performance test results of different cluster scales, see [TiDB Cloud P

The supported vCPU and RAM sizes include the following:

- 2 vCPU, 8 GiB (Beta)
- 4 vCPU, 16 GiB
- 8 vCPU, 32 GiB
- 8 vCPU, 64 GiB
- 16 vCPU, 64 GiB

> **Note:**
>
> If the vCPU and RAM size of TiKV is set as **2 vCPU, 8 GiB (Beta)** or **4 vCPU, 16 GiB**, note the following restrictions:
> If the vCPU and RAM size of TiKV is set as **4 vCPU, 16 GiB**, note the following restrictions:
>
> - The node number of TiDB can only be set to 1 or 2, and the node number of TiKV is fixed to 3.
> - 2 vCPU TiKV can only be used with 2 vCPU TiDB. 4 vCPU TiKV can only be used with 4 vCPU TiDB.
> - 4 vCPU TiKV can only be used with 4 vCPU TiDB.
> - TiFlash is unavailable.

### TiKV node number
Expand Down Expand Up @@ -168,7 +166,6 @@ The supported node storage of different TiKV vCPUs is as follows:

| TiKV vCPU | Min node storage | Max node storage | Default node storage |
|:---------:|:----------------:|:----------------:|:--------------------:|
| 2 vCPU | 200 GiB | 500 GiB | 200 GiB |
| 4 vCPU | 200 GiB | 2048 GiB | 500 GiB |
| 8 vCPU | 200 GiB | 4096 GiB | 500 GiB |
| 16 vCPU | 200 GiB | 6144 GiB | 500 GiB |
Expand All @@ -190,7 +187,7 @@ The supported vCPU and RAM sizes include the following:
- 8 vCPU, 64 GiB
- 16 vCPU, 128 GiB

Note that TiFlash is unavailable when the vCPU and RAM size of TiDB or TiKV is set as **2 vCPU, 8 GiB (Beta)** or **4 vCPU, 16 GiB**.
Note that TiFlash is unavailable when the vCPU and RAM size of TiDB or TiKV is set as **4 vCPU, 16 GiB**.

### TiFlash node number

Expand Down
29 changes: 0 additions & 29 deletions tidb-cloud/tidb-cloud-performance-reference.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,35 +13,6 @@ This document provides [Sysbench](https://github.com/akopytov/sysbench) performa

In this document, the transaction models `Read Only`, `Read Write`, and `Write Only` represent read workloads, mixed workloads, and write workloads.

## 2 vCPU performance

Currently, the 2 vCPU support of TiDB and TiKV is still in beta.

Test scales:

- TiDB (2 vCPU, 8 GiB) \* 1; TiKV (2 vCPU, 8 GiB) \* 3
- TiDB (2 vCPU, 8 GiB) \* 2; TiKV (2 vCPU, 8 GiB) \* 3

Test results:

**TiDB (2 vCPU, 8 GiB) \* 1; TiKV (2 vCPU, 8 GiB) \* 3**

| Transaction model | Threads | QPS | TPS | Average latency (ms) | P95 latency (ms) |
|-------------------|---------|----------|--------|----------------------|------------------|
| Read Only | 15 | 3,496.77 | 218.55 | 68.63 | 95.81 |
| Read Write | 5 | 1,545.90 | 77.29 | 64.68 | 94.10 |
| Write Only | 40 | 4,326.57 | 721.10 | 55.47 | 90.78 |

**TiDB (2 vCPU, 8 GiB) \* 2; TiKV (2 vCPU, 8 GiB) \* 3**

Test results:

| Transaction model | Threads | QPS | TPS | Average latency (ms) | P95 latency (ms) |
|-------------------|---------|----------|----------|----------------------|------------------|
| Read Only | 30 | 7,584.08 | 474.00 | 63.29 | 99.33 |
| Read Write | 10 | 2,680.58 | 134.03 | 74.61 | 104.84 |
| Write Only | 80 | 7,618.77 | 1,269.79 | 63.00 | 97.55 |

## 4 vCPU performance

Test scales:
Expand Down
Loading