benchmark, TOC: add 4.0 TPC-H, TPC-C and Sysbench test reports by TomShawn · Pull Request #2661 · pingcap/docs

TomShawn · 2020-06-02T06:41:21Z

What is changed, added or deleted? (Required)

add 4.0 TPC-H， TPC-C and Sysbench test reports.

Which TiDB version(s) do your changes apply to? (Required)

If you select two or more versions from above, to trigger the bot to cherry-pick this PR to your desired release version branch(es), you must add corresponding labels such as needs-cherry-pick-4.0, needs-cherry-pick-3.1, needs-cherry-pick-3.0, and needs-cherry-pick-2.1.

What is the related PR or file link(s)?

This PR is translated from: benchmark: Add TPC-H benchmark and update TPC-C benchmark for v4.0 vs v3.0 docs-cn#3392 Add v4.0 sysbench and TPC-C benchmark report docs-cn#3452 Fix typos in 4.0 test report docs-cn#3462
Other reference link(s):

JaySon-Huang · 2020-06-03T02:37:30Z

 ---
 title: TiDB TPC-C Performance Test Report -- v4.0 vs. v3.0
-summary: Compares the TPC-C performance of TiDB 4.0 and TiDB 3.0 using BenchmarkSQL.
+summary: Compare the TPC-H performance of TiDB 4.0 and TiDB 3.0 using BenchmarkSQL.


JaySon-Huang · 2020-06-03T03:49:51Z

+        git clone https://github.com/pingcap/tidb-bench.git && cd tpch/queries
+        ```
+
+    2. Execute the query and record the executing time of the query.


Should be "Execute those queries and record the executing time of each query"?

Adopted, thanks.

JaySon-Huang · 2020-06-03T03:53:52Z

+
+ Blue lines represent v3.0;
+ Red lines represent v4.0 (data read only from TiKV);
+ Yellow lines represent v4.0 (data read from TiKV and TiFlash automatically based on intelligent choice).


We use the term "smart selection" instead of "intelligent choice" in this doc:
https://pingcap.com/docs/stable/tiflash/use-tiflash/#smart-selection

This TiFlash overview document uses Intelligent choice https://pingcap.com/docs/stable/tiflash/tiflash-overview/#intelligent-choice

yikeke · 2020-06-03T09:21:48Z

Please help review this PR, thx~ @CaitinChen

FYI @TomShawn

sre-bot · 2020-06-05T03:55:41Z

@JaySon-Huang, @scsldb, @CaitinChen, @shuke987, PTAL.

CaitinChen

My review on the TPC-H doc is done. But I think we need to add numbers to show the improvements.
And, just like other benchmark reports, we should point put "TiDB version: v3.0.13 vs. v4.0.0."
@JaySon-Huang PTAL

CaitinChen · 2020-06-04T08:02:35Z

+title: TiDB TPC-H Performance Test Report -- v4.0 vs. v3.0
+summary: Compare the TPC-H performance of TiDB 4.0 and TiDB 3.0.
+category: benchmark
+draft: true


Remove this line.

CaitinChen · 2020-06-04T08:03:31Z

+
+## Test purpose
+
+This test aims to compare the TPC-H performances of TiDB 4.0 and TiDB 3.0 in the OLAP (Online Analytical Processing) scenario.


Suggested change

This test aims to compare the TPC-H performances of TiDB 4.0 and TiDB 3.0 in the OLAP (Online Analytical Processing) scenario.

This test aims to compare the TPC-H performances of TiDB 4.0 and TiDB 3.0 in the online analytical processing (OLAP) scenario.

CaitinChen · 2020-06-04T08:13:02Z

+
+This test aims to compare the TPC-H performances of TiDB 4.0 and TiDB 3.0 in the OLAP (Online Analytical Processing) scenario.
+
+Because [TiFlash](/tiflash/tiflash-overview.md) is introduced in TiDB v4.0 that enhances the HTAP (Hybrid Transactional and Analytical Processing) performance of TiDB, the following performances are tested and compared in this report:


Suggested change

Because [TiFlash](/tiflash/tiflash-overview.md) is introduced in TiDB v4.0 that enhances the HTAP (Hybrid Transactional and Analytical Processing) performance of TiDB, the following performances are tested and compared in this report:

Because [TiFlash](/tiflash/tiflash-overview.md) is introduced in TiDB v4.0, which enhances TiDB's Hybrid Transactional and Analytical Processing (HTAP) capabilities, test objects in this report are as follows:

Reference: https://www.grammarly.com/blog/which-vs-that/

CaitinChen · 2020-06-04T08:48:56Z

+
+#### Hardware prerequisite
+
+To avoid TiKV and TiFlash racing for disk and I/O resources, mount the two NVMe SSD disks configured on EC2 as `/data1` and `/data2`. Deploy TiKV on `/data1` and deploy TiFlash on `/data2`.


Suggested change

To avoid TiKV and TiFlash racing for disk and I/O resources, mount the two NVMe SSD disks configured on EC2 as `/data1` and `/data2`. Deploy TiKV on `/data1` and deploy TiFlash on `/data2`.

To avoid TiKV and TiFlash racing for disk and I/O resources, mount the two NVMe SSD disks configured on EC2 to `/data1` and `/data2`. Deploy TiKV on `/data1` and deploy TiFlash on `/data2`.

@JaySon-Huang PTAL

Maybe "mount ... at "?

http://linuxcommand.org/lc3_man_pages/mount8.html

This tells the kernel to attach the filesystem found on device (which is of type type) at the directory dir.

CaitinChen · 2020-06-05T02:38:28Z

+
+| Query ID |  v3.0  |  v4.0 TiKV Only |  v4.0 TiKV/TiFlash Automatically |
+| :-------- | :----------- | :------------ | :-------------- |
+| 1       |    7.78s   |      7.45s  |      2.09s    |


Suggested change

| 1 | 7.78s | 7.45s | 2.09s |

| 1 | 7.78 s | 7.45 s | 2.09 s |

Same comments for the following lines.

CaitinChen · 2020-06-05T02:38:57Z

+| 21      |   11.12s   |      6.23s  |      6.26s    |
+| 22      |    4.49s   |      3.05s  |      2.31s    |
+
+![TPC-H](/media/tpch_v4vsv3.png)


Suggested change

![TPC-H](/media/tpch_v4vsv3.png)

![TPC-H](/media/tpch-v4vsv3.png)

"_" is not allowed in image names.

CaitinChen · 2020-06-05T02:49:38Z

+ Blue lines represent v3.0;
+ Red lines represent v4.0 (data read only from TiKV);
+ Yellow lines represent v4.0 (data read from TiKV and TiFlash automatically based on intelligent choice).
+ The ordinate represents the processing time of the query. The lower the ordinate, the better the performance.


Suggested change

+ The ordinate represents the processing time of the query. The lower the ordinate, the better the performance.

+ The y-axis represents the execution time of the query. The less the time, the better the performance.

CaitinChen · 2020-06-05T02:51:53Z

+
+Result description:
+
+ **v4.0 TiKV Only** means that TiDB reads data only from TiKV. Comparing this result with that of v3.0, you can learn the TPC-H performance increase after TiDB and TiKV are upgraded to v4.0.


Suggested change

+ **v4.0 TiKV Only** means that TiDB reads data only from TiKV. Comparing this result with that of v3.0, you can learn the TPC-H performance increase after TiDB and TiKV are upgraded to v4.0.

+ **v4.0 TiKV Only** means that TiDB reads data only from TiKV. The result shows that the TPC-H performance increased after TiDB and TiKV are upgraded to v4.0.

CaitinChen · 2020-06-05T04:05:30Z

+Result description:
+
+ **v4.0 TiKV Only** means that TiDB reads data only from TiKV. Comparing this result with that of v3.0, you can learn the TPC-H performance increase after TiDB and TiKV are upgraded to v4.0.
+ **v4.0 TiKV/TiFlash Automatically** means that the TiDB optimizer automatically determines whether to use the TiFlash replica according to the cost estimation. Comparing this result with that of v3.0, you can learn the TPC-H performance increase in the full HTAP form of v4.0.


Suggested change

+ **v4.0 TiKV/TiFlash Automatically** means that the TiDB optimizer automatically determines whether to use the TiFlash replica according to the cost estimation. Comparing this result with that of v3.0, you can learn the TPC-H performance increase in the full HTAP form of v4.0.

+ **v4.0 TiKV/TiFlash Automatically** means that the TiDB optimizer automatically determines whether to read data from the TiFlash replica according to the cost estimation. The result shows that the TPC-H performance increased in the full HTAP form of v4.0.

CaitinChen

My review on the TPC-C doc is done.

CaitinChen · 2020-06-05T07:47:49Z

 ## Test purpose

-This test aims to compare the TPC-C performance of TiDB 4.0 and TiDB 3.0.
+This test aims to compare the TPC-C performances of TiDB 4.0 and TiDB 3.0 in the OLTP (Online Transactional Processing) scenario.


Suggested change

This test aims to compare the TPC-C performances of TiDB 4.0 and TiDB 3.0 in the OLTP (Online Transactional Processing) scenario.

This test aims to compare the TPC-C performances of TiDB 4.0 and TiDB 3.0 in the Online Transactional Processing (OLTP) scenario.

CaitinChen · 2020-06-05T07:58:06Z

+        git clone https://github.com/pingcap/benchmarksql && cd benchmarksql && ant
+        ```
+
+    2. Enter the `run` directory, edit the `props.mysql` file according to the actual situation. Modify the `conn`, `warehouses`, `loadWorkers`, `terminals`, and `runMins` configuration items.


Suggested change

2. Enter the `run` directory, edit the `props.mysql` file according to the actual situation. Modify the `conn`, `warehouses`, `loadWorkers`, `terminals`, and `runMins` configuration items.

2. Enter the `run` directory, edit the `props.mysql` file according to the actual situation, and modify the `conn`, `warehouses`, `loadWorkers`, `terminals`, and `runMins` configuration items.

CaitinChen · 2020-06-05T08:00:43Z

+
+    4. Execute the `runSQL.sh ./props.mysql sql.mysql/indexCreates.sql` command.
+
+    5. Execute MySQL client and execute the `analyze table` statement on every table.


Suggested change

5. Execute MySQL client and execute the `analyze table` statement on every table.

5. Run the MySQL client and execute the `analyze table` statement on every table.

CaitinChen · 2020-06-05T08:04:07Z

+According to the test statistics, the TPC-C performance of TiDB v4.0 has **increased by 50%** compared with that of TiDB v3.0.

-According to the testing statistics, the performance of TiDB 4.0.0-rc **has increased by 45%** than that of TiDB 3.0.8.
+![TPC-C](/media/tpcc_v4vsv3.png)


Suggested change

![TPC-C](/media/tpcc_v4vsv3.png)

![TPC-C](/media/tpcc-v4vsv3.png)

"_" is not allowed in our figure names.

CaitinChen

My review on the Sysbench doc is done.

CaitinChen · 2020-06-05T08:20:38Z

+
+## Test purpose
+
+This test aims to compare the Sysbench performances of TiDB 4.0 and TiDB 3.0 in the OLTP (Online Transactional Processing) scenario.


Suggested change

This test aims to compare the Sysbench performances of TiDB 4.0 and TiDB 3.0 in the OLTP (Online Transactional Processing) scenario.

This test aims to compare the Sysbench performances of TiDB 4.0 and TiDB 3.0 in the Online Transactional Processing (OLTP) scenario.

CaitinChen · 2020-06-05T08:21:16Z

+
+| Service type   | Software version    |
+|:----------|:-----------|
+| PD        | 3.0、4.0   |


Suggested change

| PD | 3.0、4.0 |

| PD | 3.0 and 4.0 |

CaitinChen · 2020-06-05T08:21:23Z

+| Service type   | Software version    |
+|:----------|:-----------|
+| PD        | 3.0、4.0   |
+| TiDB      | 3.0、4.0   |


CaitinChen · 2020-06-05T08:21:34Z

+|:----------|:-----------|
+| PD        | 3.0、4.0   |
+| TiDB      | 3.0、4.0   |
+| TiKV      | 3.0、4.0   |


CaitinChen · 2020-06-05T08:21:52Z

+{{< copyable "" >}}
+
+```yaml
+log.level: “error”


Suggested change

log.level: “error”

log.level: "error"

CaitinChen · 2020-06-05T09:20:36Z

+
+Compared with v3.0, the Point Select performance of TiDB v4.0 has increased by 14%.
+
+![Point Select](/media/sysbench_v4vsv3_point_select.png)


Suggested change

![Point Select](/media/sysbench_v4vsv3_point_select.png)

![Point Select](/media/sysbench-v4vsv3-point-select.png)

"_" is not allowed in our figure names.

CaitinChen · 2020-06-05T09:31:12Z

+
+Compared with v3.0, the Update Non-index performance of TiDB v4.0 has increased by 15%.
+
+![Update Non-index](/media/sysbench_v4vsv3_update_non_index.png)


Suggested change

![Update Non-index](/media/sysbench_v4vsv3_update_non_index.png)

![Update Non-index](/media/sysbench-v4vsv3-update-non-index.png)

CaitinChen · 2020-06-05T09:31:46Z

+
+Compared with v3.0, the Update Index performance of TiDB v4.0 has increased by 17%.
+
+![Update Index](/media/sysbench_v4vsv3_update_index.png)


Suggested change

![Update Index](/media/sysbench_v4vsv3_update_index.png)

![Update Index](/media/sysbench-v4vsv3-update-index.png)

CaitinChen · 2020-06-05T09:36:30Z

+
+![Update Index](/media/sysbench_v4vsv3_update_index.png)
+
+### Read Write performance


Suggested change

### Read Write performance

### Read-write performance

CaitinChen · 2020-06-05T09:36:46Z

+
+### Read Write performance
+
+Compared with v3.0, the Read Write performance of TiDB v4.0 has increased by 31%.


Suggested change

Compared with v3.0, the Read Write performance of TiDB v4.0 has increased by 31%.

Compared with v3.0, the read-write performance of TiDB v4.0 has increased by 31%.

TomShawn · 2020-06-05T11:23:57Z

@CaitinChen @JaySon-Huang Comments addressed, PTAL again.

CaitinChen · 2020-06-05T11:43:27Z

+4. Extract the tpmC data of New Order from the result.

-## Test result
+### Test result


Suggested change

### Test result

## Test result

CaitinChen · 2020-06-05T11:43:41Z

 ```

-### Cluster topology
+### Test plan


Suggested change

### Test plan

## Test plan

CaitinChen · 2020-06-05T11:46:06Z

+set global tidb_index_lookup_join_concurrency = 16;
+```
+
+### Test plan


Suggested change

### Test plan

## Test plan

CaitinChen · 2020-06-05T11:46:21Z

+
+### Test plan
+
+#### Hardware prerequisite


Suggested change

#### Hardware prerequisite

### Hardware prerequisite

CaitinChen · 2020-06-05T11:46:42Z

+
+To avoid TiKV and TiFlash racing for disk and I/O resources, mount the two NVMe SSD disks configured on EC2 to `/data1` and `/data2`. Deploy TiKV on `/data1` and deploy TiFlash on `/data2`.
+
+#### Test process


Suggested change

#### Test process

### Test process

CaitinChen · 2020-06-05T11:47:10Z

+
+4. Extract and organize the data of query execution time.
+
+### Test result


Suggested change

### Test result

## Test result

CaitinChen

LGTM

JaySon-Huang

LGTM

Signed-off-by: sre-bot <sre-bot@pingcap.com>

sre-bot · 2020-06-05T12:37:18Z

cherry pick to release-4.0 in PR #2711

#2711) * cherry pick #2661 to release-4.0 Signed-off-by: sre-bot <sre-bot@pingcap.com> * resolve conflict Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>

add TPC-H benchmark test report

6efe1f5

TomShawn added translation/from-docs-cn This PR is translated from a PR in pingcap/docs-cn. status/PTAL This PR is ready for reviewing. needs-cherry-pick-4.0 labels Jun 2, 2020

TomShawn requested review from JaySon-Huang and yikeke June 2, 2020 06:41

Add 4.0 tpcc,tpch and sysbench test reports

e86b8b9

TomShawn changed the title ~~add 4.0 TPC-H benchmark test report~~ add 4.0 TPC-H， TPC-C and Sysbench test reports Jun 2, 2020

TomShawn requested review from scsldb and shuke987 June 2, 2020 12:35

Update benchmark-sysbench-v4-vs-v3.md

ecb9aca

JaySon-Huang reviewed Jun 3, 2020

View reviewed changes

yikeke requested review from CaitinChen and removed request for yikeke June 3, 2020 09:21

CaitinChen changed the title ~~add 4.0 TPC-H， TPC-C and Sysbench test reports~~ benchmark, TOC: add 4.0 TPC-H, TPC-C and Sysbench test reports Jun 4, 2020

CaitinChen reviewed Jun 5, 2020

View reviewed changes

Merge branch 'master' into tpc-h-4.0

293f982

CaitinChen reviewed Jun 5, 2020

View reviewed changes

Merge branch 'master' into tpc-h-4.0

38a5805

CaitinChen reviewed Jun 5, 2020

View reviewed changes

address comments

6e57f4f

TomShawn added 2 commits June 5, 2020 19:43

remove s

c8cbf06

address comment and add tpch result

333fa15

CaitinChen reviewed Jun 5, 2020

View reviewed changes

TomShawn added 2 commits June 5, 2020 20:11

correct headinglevel

97a2f0e

Update v4.0-performance-benchmarking-with-tpcc.md

919e9d6

CaitinChen approved these changes Jun 5, 2020

View reviewed changes

JaySon-Huang approved these changes Jun 5, 2020

View reviewed changes

JaySon-Huang and others added 2 commits June 5, 2020 20:27

Merge branch 'master' into tpc-h-4.0

b45bb76

update tpcc image

8a544cf

TomShawn merged commit f11484c into pingcap:master Jun 5, 2020

sre-bot pushed a commit to sre-bot/docs that referenced this pull request Jun 5, 2020

cherry pick pingcap#2661 to release-4.0

a47c625

Signed-off-by: sre-bot <sre-bot@pingcap.com>

sre-bot mentioned this pull request Jun 5, 2020

benchmark, TOC: add 4.0 TPC-H, TPC-C and Sysbench test reports (#2661) #2711

Merged

5 tasks

TomShawn deleted the tpc-h-4.0 branch June 5, 2020 12:38


		## Test purpose

		This test aims to compare the TPC-H performances of TiDB 4.0 and TiDB 3.0 in the OLAP (Online Analytical Processing) scenario.


		This test aims to compare the TPC-H performances of TiDB 4.0 and TiDB 3.0 in the OLAP (Online Analytical Processing) scenario.

		Because [TiFlash](/tiflash/tiflash-overview.md) is introduced in TiDB v4.0 that enhances the HTAP (Hybrid Transactional and Analytical Processing) performance of TiDB, the following performances are tested and compared in this report:


		#### Hardware prerequisite

		To avoid TiKV and TiFlash racing for disk and I/O resources, mount the two NVMe SSD disks configured on EC2 as `/data1` and `/data2`. Deploy TiKV on `/data1` and deploy TiFlash on `/data2`.

	\| 1 \| 7.78s \| 7.45s \| 2.09s \|
	\| 1 \| 7.78 s \| 7.45 s \| 2.09 s \|

	![TPC-H](/media/tpch_v4vsv3.png)
	![TPC-H](/media/tpch-v4vsv3.png)

	+ The ordinate represents the processing time of the query. The lower the ordinate, the better the performance.
	+ The y-axis represents the execution time of the query. The less the time, the better the performance.


		Result description:

		+ v4.0 TiKV Only means that TiDB reads data only from TiKV. Comparing this result with that of v3.0, you can learn the TPC-H performance increase after TiDB and TiKV are upgraded to v4.0.

	+ v4.0 TiKV/TiFlash Automatically means that the TiDB optimizer automatically determines whether to use the TiFlash replica according to the cost estimation. Comparing this result with that of v3.0, you can learn the TPC-H performance increase in the full HTAP form of v4.0.
	+ v4.0 TiKV/TiFlash Automatically means that the TiDB optimizer automatically determines whether to read data from the TiFlash replica according to the cost estimation. The result shows that the TPC-H performance increased in the full HTAP form of v4.0.

	This test aims to compare the TPC-C performances of TiDB 4.0 and TiDB 3.0 in the OLTP (Online Transactional Processing) scenario.
	This test aims to compare the TPC-C performances of TiDB 4.0 and TiDB 3.0 in the Online Transactional Processing (OLTP) scenario.

	2. Enter the `run` directory, edit the `props.mysql` file according to the actual situation. Modify the `conn`, `warehouses`, `loadWorkers`, `terminals`, and `runMins` configuration items.
	2. Enter the `run` directory, edit the `props.mysql` file according to the actual situation, and modify the `conn`, `warehouses`, `loadWorkers`, `terminals`, and `runMins` configuration items.


		4. Execute the `runSQL.sh ./props.mysql sql.mysql/indexCreates.sql` command.

		5. Execute MySQL client and execute the `analyze table` statement on every table.

	5. Execute MySQL client and execute the `analyze table` statement on every table.
	5. Run the MySQL client and execute the `analyze table` statement on every table.

	![TPC-C](/media/tpcc_v4vsv3.png)
	![TPC-C](/media/tpcc-v4vsv3.png)


		## Test purpose

		This test aims to compare the Sysbench performances of TiDB 4.0 and TiDB 3.0 in the OLTP (Online Transactional Processing) scenario.


		Compared with v3.0, the Point Select performance of TiDB v4.0 has increased by 14%.

		![Point Select](/media/sysbench_v4vsv3_point_select.png)

	![Point Select](/media/sysbench_v4vsv3_point_select.png)
	![Point Select](/media/sysbench-v4vsv3-point-select.png)


		Compared with v3.0, the Update Non-index performance of TiDB v4.0 has increased by 15%.

		![Update Non-index](/media/sysbench_v4vsv3_update_non_index.png)

	![Update Non-index](/media/sysbench_v4vsv3_update_non_index.png)
	![Update Non-index](/media/sysbench-v4vsv3-update-non-index.png)


		Compared with v3.0, the Update Index performance of TiDB v4.0 has increased by 17%.

		![Update Index](/media/sysbench_v4vsv3_update_index.png)

	![Update Index](/media/sysbench_v4vsv3_update_index.png)
	![Update Index](/media/sysbench-v4vsv3-update-index.png)

Conversation

TomShawn commented Jun 2, 2020 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What is changed, added or deleted? (Required)

Which TiDB version(s) do your changes apply to? (Required)

What is the related PR or file link(s)?

Uh oh!

Choose a reason for hiding this comment

Uh oh!

JaySon-Huang Jun 3, 2020 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

TomShawn Jun 5, 2020 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

yikeke commented Jun 3, 2020

Uh oh!

sre-bot commented Jun 5, 2020

Uh oh!

CaitinChen left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

CaitinChen left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

CaitinChen left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

TomShawn commented Jun 2, 2020 •

edited

Loading

JaySon-Huang Jun 3, 2020 •

edited

Loading

TomShawn Jun 5, 2020 •

edited

Loading

CaitinChen left a comment •

edited

Loading


		![Update Index](/media/sysbench_v4vsv3_update_index.png)

		### Read Write performance


		### Read Write performance

		Compared with v3.0, the Read Write performance of TiDB v4.0 has increased by 31%.

	Compared with v3.0, the Read Write performance of TiDB v4.0 has increased by 31%.
	Compared with v3.0, the read-write performance of TiDB v4.0 has increased by 31%.


		To avoid TiKV and TiFlash racing for disk and I/O resources, mount the two NVMe SSD disks configured on EC2 to `/data1` and `/data2`. Deploy TiKV on `/data1` and deploy TiFlash on `/data2`.

		#### Test process


		4. Extract and organize the data of query execution time.

		### Test result