executor: add memory tracker for memtableRetriever

[wshwsh12]

What problem does this PR solve?

Issue Number: close #51456
related #51260

Problem Summary:

What changed and how does it work?

Add memory tracker for memtableRetriever

Check List

Tests

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

Test Case: 50k tables, each table contains 10 columns.

Test1: Testing 'explain analyze' to accurately display memory usage.

tidb> desc analyze select * from INFORMATION_SCHEMA.tables;
+----------------+----------+---------+------+---------------+-------------------------------------+---------------+---------+------+
| id             | estRows  | actRows | task | access object | execution info                      | operator info | memory  | disk |
+----------------+----------+---------+------+---------------+-------------------------------------+---------------+---------+------+
| MemTableScan_4 | 10000.00 | 50816   | root | table:TABLES  | time:115.1ms, loops:51, RU:0.000000 |               | 91.3 MB | N/A  |
+----------------+----------+---------+------+---------------+-------------------------------------+---------------+---------+------+
1 row in set (0.116 sec)

Test2: Testing mem-quota to successfully cancel SQL queries exceeding the threshold.

tidb> set tidb_mem_quota_query = 80 << 20;
Query OK, 0 rows affected (0.001 sec)

tidb> desc analyze select * from INFORMATION_SCHEMA.tables;
ERROR 8175 (HY000): Your query has been cancelled due to exceeding the allowed memory limit for a single SQL query. Please try narrowing your query scope or increase the tidb_mem_quota_query limit and try again.[conn=463470598]

• No need to test

  • I checked and no code files have been changed.

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

[tiprow]

Hi @wshwsh12. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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.

[codecov]

Codecov Report

Merging #51455 (da0ceed) into master (60aa838) will increase coverage by 2.7114%.
Report is 29 commits behind head on master.
The diff coverage is 100.0000%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #51455        +/-   ##
================================================
+ Coverage   70.6985%   73.4099%   +2.7114%     
================================================
  Files          1462       1463         +1     
  Lines        435210     440890      +5680     
================================================
+ Hits         307687     323657     +15970     
+ Misses       108225      97086     -11139     
- Partials      19298      20147       +849     

Flag	Coverage Δ
integration	49.7203% <100.0000%> (?)
unit	71.0142% <100.0000%> (+0.5164%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	51.7237% <ø> (+5.8787%)	⬆️

[ywqzzy]

/lgtm

[YangKeao]

LGTM

[YangKeao]

At this time, the memory has already been allocated 🤔. Do we have a plan to Consume progressively in each implementation above?

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: YangKeao, ywqzzy

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 [YangKeao,ywqzzy]

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-03-01 09:57:41.65262228 +0000 UTC m=+1215150.400245406: ☑️ agreed by ywqzzy.
• 2024-03-04 08:49:43.912291959 +0000 UTC m=+70610.934538347: ☑️ agreed by YangKeao.

[wshwsh12]

/retest

[tiprow]

@wshwsh12: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

[wshwsh12]

/retest

[tiprow]

@wshwsh12: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

[wshwsh12]

/ok-to-test

[tiprow]

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

Test name	Commit	Details	Required	Rerun command
fast_test_tiprow	da0ceed	link	true	/test fast_test_tiprow

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.

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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