doc/tidb-cloud add v.7.10 sysbench test result #13756
Conversation
|
[REVIEW NOTIFICATION] This pull request has not been approved. To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
ti-chi-bot
bot
added
first-time-contributor
|
|
||
| ### Parameter configuration | ||
|
|
||
| Enabling the below parameter can have a positive impact on performance in the 'oltp_insert','oltp_read_write','oltp_update_index','oltp_update_non_index' scenario. |
There was a problem hiding this comment.
IMO, it would be better to say log recycling, which is enabled by default in v6.3.0, can improve the performance of these 4 scenarios. Enabling the below parameter can let the log recycling effective immediately after initialization, speeding up the benchmark. https://docs.pingcap.com/tidb/dev/tikv-configuration-file#prefill-for-recycle-new-in-v700
| ``` | ||
|
|
||
| #### How to edit tikv config | ||
| we recommend contacting our support team. Our support team is available to assist you with parameter modifications according to your specific requirements. |
There was a problem hiding this comment.
Need to double-check the support team.
ti-chi-bot
bot
removed
the
missing-translation-status
Signed-off-by: Aolin <aolin.zhang@pingcap.com>
Oreoxmt
added
do-not-merge/hold
| prepare --tables=32 --table-size=10000000 | ||
| ``` | ||
|
|
||
| 4. Run the following `sysbench run` command to conduct stress tests on the TiDB Dedicated cluster. For each concurrency, the test takes 20 minutes. This document conducts tests on five workloads: `oltp_point_select`, `oltp_read_write`, `oltp_update_non_index`, `oltp_update_index`, and `oltp_insert`. For each workload, this document conducts three tests with the `${THREAD}` value of `100`, `200`, and `400`. |
There was a problem hiding this comment.
"For each concurrency", what does "each concurrency" mean?
There was a problem hiding this comment.
--timelimits the total execution time in seconds.
For each workload, the following sysbench run command is executed 3 times, each time with a different level of concurrency (the number of threads) specified by ${THREAD}.
sysbench ${WORKLOAD} run \
--mysql-host=${HOST} \
--mysql-port=${PORT} \
--mysql-user=root \
--db-driver=mysql \
--mysql-db=sbtest \
--threads=${THREAD} \
--time=1200 \
--report-interval=10 \
--tables=32 \
--table-size=10000000 \
--mysql-ignore-errors=1062,2013,8028,9007 \
--auto-inc=false \
--mysql-password=${PASSWORD}
Co-authored-by: Grace Cai <qqzczy@126.com>
|
@Yui-Song: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@qiancai PTAL again |
Co-authored-by: Grace Cai <qqzczy@126.com>
ti-chi-bot
bot
added
lgtm
and removed
needs-1-more-lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Oreoxmt, qiancai, Yui-Song The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Oreoxmt
removed
the
do-not-merge/hold
First-time contributors' checklist
What is changed, added or deleted? (Required)
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?