Storages: Add Block pop-up latency metrics

[JinheLin]

What problem does this PR solve?

Issue Number: ref #9417, #6834

Problem Summary:

What is changed and how it works?

• Block pop-up latency when a query is heavy (sometime it means computing is the bottleneck):
  

• Block pop-up latency when a query is light (sometime it means storage is the bottleneck):
  

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

[CalvinNeo]

lgtm

[Lloyd-Pottiger]

How about recording the latency of both popBlock and pushBlock?

[JinheLin]

How about recording the latency of both popBlock and pushBlock?

Do you mean the cost time of popBlock and pushBlock?

Except for mutex lock, pushBlock never wait, because the max-size of the queue is unlimited inside WorkQueue. (We limit the size of the queue in SegmentReadTaskScheduler.)

For popBlock, currently tryPopBlock is used to replace popBlock, and it is never blocked, except for mutex lock.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: CalvinNeo, Lloyd-Pottiger

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 [CalvinNeo,Lloyd-Pottiger]

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-07-26 11:21:12.174058133 +0000 UTC m=+4756.301118284: ☑️ agreed by CalvinNeo.
• 2024-07-29 09:52:31.129772891 +0000 UTC m=+176667.409820970: ☑️ agreed by Lloyd-Pottiger.

[ti-chi-bot]

@JinheLin: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

trigger some heavy tests which will not run always when PR updated.

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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 ti-community-infra/tichi repository.

[JinheLin]

/retest

[ti-chi-bot]

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

[ti-chi-bot]

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