Storages: Update the length of Block queue and the number of read threads

[JinheLin]

What problem does this PR solve?

Issue Number: close #8703

What is changed and how it works?

• The length of Block queue:

  • For on-premise deployment, adjusting the length of the Block queue to 1.5 times of the current default value is expected to reduce the time required for simple queries by 3-6%.
  • For disaggregated deployment, adjusting the length of the Block queue to 1.5 times of the current default value is expected to reduce the time required for simple queries by 2-20%. The specific performance improvement depends on data caching. The less cached data, the more significant the improvement.

• The number of read threads:

  • For disaggregated deployment, if most of the data cannot hit the local disk cache, the network will become a bottleneck, and increasing the number of threads can significantly improve performance. If more than half of the data is expected to hit the local cache, adjusting the number of threads to 2 times of the current default value is enough.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

None

[JaySon-Huang]

LGTM

I think it should be picked back to release-7.5 at least. What about the release-6.5 and release-6.1?

[JinheLin]

LGTM

I think it should be picked back to release-7.5 at least. What about the release-6.5 and release-6.1?

Yes. I will update the issue later.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JaySon-Huang, Lloyd-Pottiger

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 [JaySon-Huang,Lloyd-Pottiger]

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]

[LGTM Timeline notifier]

Timeline:

• 2024-01-18 08:11:58.827087768 +0000 UTC m=+429960.391385473: ☑️ agreed by JaySon-Huang.
• 2024-01-18 10:09:20.676115902 +0000 UTC m=+437002.240413628: ☑️ agreed by Lloyd-Pottiger.

[ti-chi-bot]

@JinheLin: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

trigger some heavy tests which will not run always when PR updated.

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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 ti-community-infra/tichi repository.

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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