*: GC-aware memory track for analyze (#35248)

[ti-srebot]

cherry-pick #35248 to release-6.1
You can switch your code base to this Pull Request by using git-extras:

# In tidb repo:
git pr https://github.com/pingcap/tidb/pull/36380

After apply modifications, you can push your change to this PR via:

git push git@github.com:ti-srebot/tidb.git pr/36380:release-6.1-fd6f5dd79827

---

What problem does this PR solve?

Issue Number: close #34996 ref #33054

Problem Summary:
Resolve the gap of analyze memory track which is caused by gc trigger.

What is changed and how it works?

mysql> set global tidb_mem_quota_analyze=8589934592; // 8GB
mysql> analyze tpcc.customer with 0.05 samplerate;
Before:
success

After:
ERROR 1105 (HY000): analyze panic due to memory quota exceeds, please try with smaller samplerate(refer to 110000/count)

set 5G quota;
analyze table zto_ssmx_bill_detail; (with 160+ columns, 5G quota)
ERROR 1105 (HY000): analyze panic due to memory quota exceeds, please try with smaller samplerate(refer to 110000/count)

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 not been approved.

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-srebot]

/run-all-tests

[ti-srebot]

@chrysan please accept the invitation then you can push to the cherry-pick pull requests. Comment with /cherry-pick-invite if the invitation is expired.
https://github.com/ti-srebot/tidb/invitations

[ti-chi-bot]

@ti-srebot: PR needs rebase.

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.

[ti-chi-bot]

@ti-srebot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/unit-test	ae418a4	link	true	/test unit-test
idc-jenkins-ci-tidb/check_dev	ae418a4	link	true	/test check-dev
idc-jenkins-ci-tidb/mysql-test	ae418a4	link	true	/test mysql-test
idc-jenkins-ci-tidb/check_dev_2	ae418a4	link	true	/test check-dev2
idc-jenkins-ci-tidb/build	ae418a4	link	true	/test build

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.