infoschema: support evict by lru cache size

[tiancaiamao]

What problem does this PR solve?

Issue Number: close #52237

Problem Summary:

What changed and how does it work?

Before this change, the lru cache evict is based on count.
This commit intend to support evict based on size.
Since the original sieve package does not support such operation, I modify the code base on it.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• 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 @tiancaiamao. 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 #52423 (45e4758) into master (f01f305) will increase coverage by 0.1141%.
Report is 1 commits behind head on master.
The diff coverage is 81.1158%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #52423        +/-   ##
================================================
+ Coverage   74.2977%   74.4119%   +0.1141%     
================================================
  Files          1471       1476         +5     
  Lines        354568     427578     +73010     
================================================
+ Hits         263436     318169     +54733     
- Misses        71821      89572     +17751     
- Partials      19311      19837       +526     

Flag	Coverage Δ
integration	48.9814% <62.2317%> (?)
unit	71.1962% <81.1158%> (-1.8544%)	⬇️

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

Components	Coverage Δ
dumpling	53.9957% <ø> (-2.3014%)	⬇️
parser	∅ <ø> (∅)
br	49.7765% <ø> (+7.0733%)	⬆️

[GMHDBJD]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: GMHDBJD, 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 [GMHDBJD,ywqzzy]
• pkg/infoschema/OWNERS [GMHDBJD,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-04-16 05:49:59.79643289 +0000 UTC m=+317218.907479340: ☑️ agreed by GMHDBJD.
• 2024-04-17 06:46:41.184009167 +0000 UTC m=+407020.295055611: ☑️ agreed by ywqzzy.

[tiprow]

@tiancaiamao: 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	7c36f4c	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]

@tiancaiamao: 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
pull-lightning-integration-test	7b66ef9	link	true	/test pull-lightning-integration-test

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.

[tiancaiamao]

/test unit-test

[tiprow]

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

In response to this:

/test unit-test

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]

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