PageStorage: Log down the gc time for external pages (#5739)

[ti-chi-bot]

This is an automated cherry-pick of #5739

What problem does this PR solve?

Issue Number: ref #5697

Problem Summary:
The GC total time in logging does not include the time costs in clean_external_page.

What is changed and how it works?

• Add a struct GCTimeStatistics to handle logging
• Add the time cost in cleanExternalPage into GC total time
• Add ExternalIdsByNamespace to
  • Manage external ids by namespace
  • Shorten the GC time of cleaning external pages from 2500+ms to 420ms with about 5000 empty tables

# before
[2022/08/31 13:06:27.762 +08:00] [DEBUG] [PageStorageImpl.cpp:330] ["PageStorage:__global__.data GC finished without full gc. [total time=2514ms] [dump snapshots=0ms] [gc in mem entries=1ms] [blobstore remove entries=0ms] [blobstore get status=0ms] [get gc entries=0ms] [blobstore full gc=0ms] [gc apply=0ms] [external callbacks=4933] [external gc=2512ms] [get alive=2098.75ms] [scanner=408.65ms] [remover=4.90ms]"] [thread_id=163]

# after
[2022/08/31 13:10:22.715 +08:00] [DEBUG] [PageStorageImpl.cpp:330] ["PageStorage:__global__.data GC finished without full gc. [total time=427ms] [dump snapshots=0ms] [gc in mem entries=1ms] [blobstore remove entries=0ms] [blobstore get status=0ms] [get gc entries=0ms] [blobstore full gc=0ms] [gc apply=0ms] [external callbacks=4933] [external gc=425ms] [get alive=14.70ms] [scanner=407.08ms] [remover=3.83ms]"] [thread_id=136]

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

[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-chi-bot]

@ti-chi-bot: This cherry pick PR is for a release branch and has not yet been approved by release team.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved by the collaborators.

AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review.

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.

[flowbehappy]

I think we don't need to pick to v6.1

[JaySon-Huang]

closed as not planned to enable ps v3 in 6.1.x