Skip to content

Commit

Permalink
Preview PR pingcap/docs#19558 and this preview is triggered from commit
Browse files Browse the repository at this point in the history
  • Loading branch information
Docsite Preview Bot committed Dec 10, 2024
1 parent fbfd981 commit 6692a4a
Show file tree
Hide file tree
Showing 7 changed files with 22 additions and 17 deletions.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified markdown-pages/en/tidbcloud/master/media/tidb-cloud/v8.5.0_tpcc.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
Expand Up @@ -199,9 +199,13 @@ This section introduces how to perform the Sysbench performance test step by ste
oltp_common prepare
```

for i in {1..12}; do
mysql -u root -h tidb-0 -P 4000 test -e "ANALYZE TABLE sbtest$i"
done

To verify the data import, run the following command:

```shell
for i in {1..12}; do
mysql -u root -h ${HOST} -P ${PORT} -p ${PASSWORD} sbtest -e "ANALYZE TABLE sbtest$i"
done
```

4. Run the following `sysbench run` command to warm up Sysbench performance tests on different workloads. Replace `${HOST}`, `${PORT}`, `${THREAD}`, and `${PASSWORD}` with your actual values.
Expand Down Expand Up @@ -323,7 +327,7 @@ This section introduces the Sysbench performance of v8.5.0 in the [test environm

The performance on the `oltp_point_select` workload is as follows:

| Threads | TPS | 95% latency (ms)| Tuning mode TPS | 95% latency (ms) |
| Threads | General mode TPS | 95% latency (ms)| Tuning mode TPS | 95% latency (ms) |
|:--------|:----------|:----------|:----------|:----------|
| 50 | 32,081 | 2.00 | 33,038 | 1.89 |
| 100 | 60,086 | 2.11 | 63,383| 2.00 |
Expand All @@ -335,7 +339,7 @@ The performance on the `oltp_point_select` workload is as follows:

The performance on the `oltp_read_only` workload is as follows:

| Threads | TPS | 95% latency (ms)| Tuning mode TPS | 95% latency (ms) |
| Threads | General mode TPS | 95% latency (ms)| Tuning mode TPS | 95% latency (ms) |
|:--------|:----------|:----------|:----------|:----------|
| 50 | 2,099 | 28.67 | 2,064 | 29.19 |
| 100 | 3,924 | 30.81 | 3,843 | 30.81 |
Expand All @@ -347,7 +351,7 @@ The performance on the `oltp_read_only` workload is as follows:

The performance on the `oltp_write_only` workload is as follows:

| Threads | TPS | 95% latency (ms)| Tuning mode TPS | 95% latency (ms) |
| Threads | General mode TPS | 95% latency (ms)| Tuning mode TPS | 95% latency (ms) |
|:--------|:----------|:----------|:----------|:----------|
| 50 | 3,056 | 19.65 | 3,405 | 16.71 |
| 100 | 5,644 | 25.28 | 5,894 | 23.95 |
Expand All @@ -359,7 +363,7 @@ The performance on the `oltp_write_only` workload is as follows:

The performance on the `oltp_read_write` workload is as follows:

| Threads | TPS | 95% latency (ms)| Tuning mode TPS | 95% latency (ms) |
| Threads | General mode TPS | 95% latency (ms)| Tuning mode TPS | 95% latency (ms) |
|:--------|:----------|:----------|:----------|:----------|
| 50 | 1,062 | 52.89 | 1,054 |52.89 |
| 100 | 1,819 | 63.32 | 1,811 | 63.32 |
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ The test is conducted on a TiDB cluster with the following settings:
The test is conducted in the following two modes:

- General mode: uses default configurations
- Tune mode: uses optimized configurations
- Tuning mode: uses optimized configurations

The following are configurations used for tuning mode in [test steps](#test-steps):

Expand Down Expand Up @@ -74,6 +74,7 @@ The following are configurations used for tuning mode in [test steps](#test-step
[rocksdb.titan]
enabled = true
[rocksdb.defaultcf.titan]
min-blob-size = "1KB"
blob-file-compression = "zstd"
Expand Down Expand Up @@ -141,15 +142,15 @@ This section introduces how to perform the TPC-C performance test step by step.

1. The test in this document is implemented based on [go-tpc](https://github.com/pingcap/go-tpc). You can download the test program using the following command:

```shell
curl --proto '=https' --tlsv1.2 -sSf https://raw.githubusercontent.com/pingcap/go-tpc/master/install.sh | sh
```
```shell
curl --proto '=https' --tlsv1.2 -sSf https://raw.githubusercontent.com/pingcap/go-tpc/master/install.sh | sh
```

2. Run the following `go-tpc tpcc` command to import 900 warehouses to the `tpcc` database. Replace `${HOST}`, `${THREAD}`, and `${PASSWORD}` with your actual values. This document conducts three tests with the `${THREAD}` value of `50`, `100`, and `200`.
2. Run the following `go-tpc tpcc` command to import 900 warehouses to the `tpcc` database. Replace `${HOST}`, `${PORT}`, `${THREAD}`, and `${PASSWORD}` with your actual values. This document conducts three tests with the `${THREAD}` value of `50`, `100`, and `200`.

```shell
go-tpc tpcc --host ${HOST} --warehouses 900 prepare -P 4000 -D tpcc -T ${THREAD} --time 2h0m0s -p ${PASSWORD} --ignore-error --parts=12 --partition-type=4
```
```shell
go-tpc tpcc --host ${HOST} --warehouses 900 prepare -P ${PORT} -D tpcc -T ${THREAD} --time 2h0m0s -p ${PASSWORD} --ignore-error --parts=12 --partition-type=4
```

4. To ensure that the TiDB optimizer can generate the optimal execution plan, execute the following SQL statements to collect statistics before conducting the TPC-C test:

Expand All @@ -176,7 +177,7 @@ This section introduces how to perform the TPC-C performance test step by step.
5. Run the following command to warm up TPC-C performance tests on different workloads. Replace `${HOST}`, `${PORT}`, `${THREAD}`, and `${PASSWORD}` with your actual values.

```shell
go-tpc tpcc --host ${HOST} --warehouses 900 run -P ${HOST} -D tpcc -T ${THREAD} --time 2h0m0s -p ${PASSWORD} --ignore-error --count=1000000
go-tpc tpcc --host ${HOST} --warehouses 900 run -P ${PORT} -D tpcc -T ${THREAD} --time 2h0m0s -p ${PASSWORD} --ignore-error --count=1000000
```

6. Run the following `go-tpc tpcc` command to conduct stress tests on the TiDB Cloud Dedicated cluster.
Expand All @@ -185,7 +186,7 @@ This section introduces how to perform the TPC-C performance test step by step.
loads=("--threads=50 --count=1800000" "--threads=100 --count=2400000" "--threads=200 --count=2700000")
for load in "${loads[@]}"; do
sleep 60
go-tpc tpcc run --warehouses 900 --host {HOST} --db=tpcc $load -p ${PASSWORD} --ignore-error
go-tpc tpcc run --warehouses 900 --host ${HOST} -P ${PORT} --db=tpcc $load -p ${PASSWORD} --ignore-error
done
```

Expand Down

0 comments on commit 6692a4a

Please sign in to comment.