Add some explanation for tiflash tuning performance doc

[CrystalAnalyst]

First-time contributors' checklist

• I've signed Contributor License Agreement that's required for repo owners to accept my contribution.

What is changed, added or deleted? (Required)

Add some explanation for tiflash tuning performance doc

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)
• v7.6 (TiDB 7.6 versions)
• v7.5 (TiDB 7.5 versions)
• v7.4 (TiDB 7.4 versions)
• v7.3 (TiDB 7.3 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)
• v6.1 (TiDB 6.1 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)

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

• This PR is translated from: Add some explanation for tiflash tuning performance doc docs-cn#15496
• Other reference 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

[CLAassistant]

All committers have signed the CLA.

[ti-chi-bot]

Welcome @CrystalAnalyst!

It looks like this is your first PR to pingcap/docs 🎉.

I'm the bot to help you request reviewers, add labels and more, See available commands.

We want to make sure your contribution gets all the attention it needs!



Thank you, and welcome to pingcap/docs. 😃

[dveeden]

From the linter:

tiflash/tune-tiflash-performance.md: 310: MD012/no-multiple-blanks Multiple consecutive blank lines [Expected: 1; Actual: 2]

[rpaik]

Thanks for your contribution to TiDB Docs Dash @CrystalAnalyst 🎊

[CrystalAnalyst]

@Oreoxmt @qiancai Hi ~ would you take some time review my changes ? I'd appreciated that, thanks!

[CrystalAnalyst]

@Oreoxmt Sorry to bother, but the DDL is approaching, can you review and approve the change ? If there's still room for improvement, I'm glad to change.

[Oreoxmt]

@CrystalAnalyst

Thank you for reaching out, and no worries at all. Just to clarify, the deadline for this TiDB Docs Dash event is to merge this PR before January 26th (see https://www.pingcap.com/event/tidb-docs-dash/). Currently, we're handling a significant backlog of PRs waiting for review. I'll prioritize reviewing and merging your PR, but it might take a bit of time due to the high volume of pending requests.

[CrystalAnalyst]

@CrystalAnalyst

Thank you for reaching out, and no worries at all. Just to clarify, the deadline for this TiDB Docs Dash event is to merge this PR before January 26th (see https://www.pingcap.com/event/tidb-docs-dash/). Currently, we're handling a significant backlog of PRs waiting for review. I'll prioritize reviewing and merging your PR, but it might take a bit of time due to the high volume of pending requests.

Oh! I see. Wish you good luck!

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-01-09 10:59:59.011472959 +0000 UTC m=+354588.595726637: ☑️ agreed by dveeden.
• 2024-01-24 02:21:09.751562531 +0000 UTC m=+927311.315860220: ☑️ agreed by Oreoxmt.

[ran-huang]

rest LGTM

[Oreoxmt]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Oreoxmt

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:

• OWNERS [Oreoxmt]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #16251.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.6: #16254.