Skip to content

performance tuning: overview + OLTP practices #8752

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 21 commits into from
Jun 10, 2022
Merged

performance tuning: overview + OLTP practices #8752

merged 21 commits into from
Jun 10, 2022

Conversation

qiancai
Copy link
Collaborator

@qiancai qiancai commented May 30, 2022 •
edited
Loading

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.

  • master (the latest development version)
  • v6.1 (TiDB 6.1 versions)
  • v6.0 (TiDB 6.0 versions)
  • v5.4 (TiDB 5.4 versions)
  • v5.3 (TiDB 5.3 versions)
  • v5.2 (TiDB 5.2 versions)
  • v5.1 (TiDB 5.1 versions)
  • v5.0 (TiDB 5.0 versions)
  • v4.0 (TiDB 4.0 versions)

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

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

@ti-chi-bot
Copy link
Member

ti-chi-bot commented May 30, 2022 •
edited
Loading

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • hfxsd

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot requested a review from shichun-0415 May 30, 2022 02:13
@ti-chi-bot ti-chi-bot added missing-translation-status This PR does not have translation status info. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels May 30, 2022
@qiancai qiancai requested review from shaoxiqian and dbsid May 30, 2022 02:14
@qiancai qiancai added the translation/from-docs-cn This PR is translated from a PR in pingcap/docs-cn. label May 30, 2022
@ti-chi-bot ti-chi-bot removed the missing-translation-status This PR does not have translation status info. label May 30, 2022
@qiancai qiancai added v6.1 This PR/issue applies to TiDB v6.1. area/diagnosis Indicates that the Issue or PR belongs to the area of diagnosis and monitoring. labels May 30, 2022
shaoxiqian
shaoxiqian reviewed May 30, 2022
View reviewed changes
performance-tuning-practices.md Outdated

## Environment description

This document takes an OLTP simulation workload of a bank transaction system for demonstration. The configurations of the simulation environment are as follows:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a bank core system

shaoxiqian
shaoxiqian reviewed May 30, 2022
View reviewed changes
performance-tuning-practices.md Outdated
This document takes an OLTP simulation workload of a bank transaction system for demonstration. The configurations of the simulation environment are as follows:

- Application development language for the workload: JAVA
- SQL statements used in business: 200 statements in total, 90% of which are SELECT statements. It is a typical read-intensive OLTP scenario.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is a typical read-intensive OLTP scenario----->It is a typical read-heavy OLTP workload ?

qiancai
qiancai commented May 31, 2022
View reviewed changes
qiancai
qiancai commented May 31, 2022
View reviewed changes
qiancai
qiancai commented May 31, 2022
View reviewed changes
hfxsd
hfxsd reviewed Jun 6, 2022
View reviewed changes
hfxsd
hfxsd reviewed Jun 6, 2022
View reviewed changes
hfxsd
hfxsd reviewed Jun 7, 2022
View reviewed changes
qiancai and others added 4 commits June 7, 2022 15:31
@qiancai @hfxsd
Update performance-tuning-practices.md
c54a050 
Co-authored-by: xixirangrang <hfxsd@hotmail.com>
@qiancai @hfxsd
Apply suggestions from code review
e6783df 
Co-authored-by: xixirangrang <hfxsd@hotmail.com>
@qiancai @hfxsd
Update performance-tuning-overview.md
b2dad80 
Co-authored-by: xixirangrang <hfxsd@hotmail.com>
@qiancai
update text in the user response time graphic
32f484d
qiancai
qiancai commented Jun 7, 2022
View reviewed changes
@shichun-0415 shichun-0415 added the needs-cherry-pick-release-6.1 Should cherry pick this PR to release-6.1 branch. label Jun 7, 2022
hfxsd
hfxsd approved these changes Jun 7, 2022
View reviewed changes
Copy link
Collaborator

@hfxsd hfxsd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ti-chi-bot ti-chi-bot added status/LGT1 Indicates that a PR has LGTM 1. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Jun 7, 2022
dbsid
dbsid approved these changes Jun 9, 2022
View reviewed changes
Copy link
Contributor

@dbsid dbsid left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ti-chi-bot ti-chi-bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 9, 2022
@qiancai
Copy link
Collaborator Author

qiancai commented Jun 10, 2022

/remove-status LGT1
/status LGT2

@ti-chi-bot ti-chi-bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Jun 10, 2022
@qiancai
Copy link
Collaborator Author

qiancai commented Jun 10, 2022

/merge

@ti-chi-bot
Copy link
Member

This pull request has been accepted and is ready to merge.

Commit hash: c0bab73

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Jun 10, 2022
@ti-chi-bot ti-chi-bot merged commit 7a882ba into pingcap:master Jun 10, 2022
ti-chi-bot pushed a commit to ti-chi-bot/docs that referenced this pull request Jun 10, 2022
@qiancai @ti-chi-bot
performance tuning: overview + OLTP practices (pingcap#8752)
835fb99
@ti-chi-bot ti-chi-bot mentioned this pull request Jun 10, 2022
Merged
14 tasks
@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #8890.

ti-chi-bot added a commit that referenced this pull request Jun 10, 2022
@ti-chi-bot
performance tuning: overview + OLTP practices (#8752) (#8890)
c913666
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@hfxsd hfxsd hfxsd approved these changes

@shaoxiqian shaoxiqian shaoxiqian approved these changes

@shichun-0415 shichun-0415 Awaiting requested review from shichun-0415

+1 more reviewer

@dbsid dbsid dbsid approved these changes

Reviewers whose approvals may not affect merge requirements
Assignees
No one assigned
Labels
area/diagnosis Indicates that the Issue or PR belongs to the area of diagnosis and monitoring. needs-cherry-pick-release-6.1 Should cherry pick this PR to release-6.1 branch. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. translation/from-docs-cn This PR is translated from a PR in pingcap/docs-cn. v6.1 This PR/issue applies to TiDB v6.1.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
6 participants
@qiancai @ti-chi-bot @dbsid @hfxsd @shaoxiqian @shichun-0415