statistics: reduce dumpStatsMaxDuration as 5min

[hawkingrei]

What problem does this PR solve?

Issue Number: ref #56537

Problem Summary:

What changed and how does it work?

Previously, dumpStatsMaxDuration was set to 1 hour, which is excessively long for large tables. Additionally, achieving the 1/10000 threshold for large tables is quite challenging. Therefore, we have decided to reduce the maximum interval.

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

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 56.6669%. Comparing base (329af09) to head (1a3c24e).
Report is 11 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #56538         +/-   ##
=================================================
- Coverage   73.3539%   56.6669%   -16.6871%     
=================================================
  Files          1626       1776        +150     
  Lines        449042     639998     +190956     
=================================================
+ Hits         329390     362667      +33277     
- Misses        99461     252668     +153207     
- Partials      20191      24663       +4472     

Flag	Coverage Δ
integration	38.4960% <0.0000%> (?)
unit	72.5033% <0.0000%> (+0.0378%)	⬆️

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

Components	Coverage Δ
dumpling	52.9478% <ø> (ø)
parser	∅ <ø> (∅)
br	52.5325% <ø> (+6.9523%)	⬆️

[hawkingrei]

/retest

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qw4990, winoros

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:

• pkg/statistics/OWNERS [qw4990,winoros]

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-10-10 10:08:40.928424687 +0000 UTC m=+1127076.348637699: ☑️ agreed by winoros.
• 2024-10-10 10:50:48.066018442 +0000 UTC m=+1129603.486231449: ☑️ agreed by qw4990.

[hawkingrei]

/hold

[hawkingrei]

/unhold

[hawkingrei]

/cherrypick release-8.1
/cherrypick release-7.5

[ti-chi-bot]

@hawkingrei: new pull request created to branch release-7.5: #56714.

In response to this:

/cherrypick release-8.1
/cherrypick release-7.5

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.

[ti-chi-bot]

@hawkingrei: new pull request created to branch release-8.1: #56715.

In response to this:

/cherrypick release-8.1
/cherrypick release-7.5

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.

[hawkingrei]

/cherrypick release-7.1

[ti-chi-bot]

@hawkingrei: new pull request created to branch release-7.1: #56736.

In response to this:

/cherrypick release-7.1

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.