util: set memory limit tuner to valid value after trigger tuning

[wshwsh12]

What problem does this PR solve?

Issue Number: ref #37816

Problem Summary:

Now, memory limit tuner will setMemoryLimit to MaxInt64(No limit) when the first GC is trigger by memory limit. And reset after 1 minute.
In this case, set MemoryLimit to physical memory 88% (80% global memory control default value * 1.1) is better.

What is changed and how it works?

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

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• XuHuaiyu
• hawkingrei

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.

[hawkingrei]

@wshwsh12

util/gctuner/memory_limit_tuner.go:121:7: unused-receiver: method receiver 't' is not referenced in method's body, consider removing or renaming it as _ (revive)

[XuHuaiyu]

/merge

[wshwsh12]

/merge

[ti-chi-bot]

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

Commit hash: 1e4ee9b

[sre-bot]

TiDB MergeCI notify

🔴 Bad News! New failing [1] after this pr merged.
These new failed integration tests seem to be caused by the current PR, please try to fix these new failed integration tests, thanks!

CI Name	Result	Duration	Compare with Parent commit
idc-jenkins-ci-tidb/integration-ddl-test	🟥 failed 1, success 5, total 6	5 min 28 sec	New failing
idc-jenkins-ci/integration-cdc-test	🟢 all 40 tests passed	22 min	Existing passed
idc-jenkins-ci-tidb/integration-common-test	🟢 all 17 tests passed	21 min	Existing passed
idc-jenkins-ci-tidb/common-test	🟢 all 11 tests passed	10 min	Existing passed
idc-jenkins-ci-tidb/mybatis-test	🟢 all 1 tests passed	6 min 27 sec	Existing passed
idc-jenkins-ci-tidb/sqllogic-test-2	🟢 all 28 tests passed	6 min 8 sec	Existing passed
idc-jenkins-ci-tidb/tics-test	🟢 all 1 tests passed	5 min 58 sec	Existing passed
idc-jenkins-ci-tidb/sqllogic-test-1	🟢 all 26 tests passed	4 min 42 sec	Existing passed
idc-jenkins-ci-tidb/integration-compatibility-test	🟢 all 1 tests passed	2 min 48 sec	Existing passed
idc-jenkins-ci-tidb/plugin-test	🟢 build success, plugin test success	4min	Existing passed