Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

increase bg gc check interval #5056

Merged
merged 2 commits into from
Jun 3, 2022

Conversation

lidezhu
Copy link
Contributor

@lidezhu lidezhu commented Jun 2, 2022

What problem does this PR solve?

Issue Number: close #5057

Problem Summary: The background gc check interval is too short and may consume some unnecessary resource consumption.

What is changed and how it works?

Increase background gc check interval from 5 seconds to 60 seconds.

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
Copy link
Member

ti-chi-bot commented Jun 2, 2022

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • JinheLin
  • Lloyd-Pottiger

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 added do-not-merge/needs-linked-issue release-note-none Denotes a PR that doesn't merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. needs-cherry-pick-release-5.0 PR which needs to be cherry-picked to release-5.0 needs-cherry-pick-release-5.1 PR which needs to be cherry-picked to release-5.1 needs-cherry-pick-release-5.2 PR which needs to be cherry-picked to release-5.2 needs-cherry-pick-release-5.3 Type: Need cherry pick to release-5.3 needs-cherry-pick-release-5.4 Should cherry pick this PR to release-5.4 branch. needs-cherry-pick-release-6.0 Type: Need cherry pick to release-6.0 needs-cherry-pick-release-6.1 Should cherry pick this PR to release-6.1 branch. and removed do-not-merge/needs-linked-issue labels Jun 2, 2022
@lidezhu lidezhu self-assigned this Jun 2, 2022
Copy link
Contributor

@Lloyd-Pottiger Lloyd-Pottiger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Jun 2, 2022
@ti-chi-bot ti-chi-bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Jun 2, 2022
@lidezhu
Copy link
Contributor Author

lidezhu commented Jun 3, 2022

/merge

@ti-chi-bot
Copy link
Member

@lidezhu: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and 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.

If you have any questions about the PR merge process, please refer to pr process.

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
Copy link
Member

This pull request has been accepted and is ready to merge.

Commit hash: b487137

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Jun 3, 2022
@sre-bot
Copy link
Collaborator

sre-bot commented Jun 3, 2022

Coverage for changed files

Filename                                                                                        Regions    Missed Regions     Cover   Functions  Missed Functions  Executed       Lines      Missed Lines     Cover    Branches   Missed Branches     Cover
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
/home/jenkins/agent/workspace/tiflash-build-common/tiflash/dbms/src/Interpreters/Settings.h           1                 0   100.00%           1                 0   100.00%           1                 0   100.00%           0                 0         -
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
TOTAL                                                                                                 1                 0   100.00%           1                 0   100.00%           1                 0   100.00%           0                 0         -

Coverage summary

Functions  MissedFunctions  Executed  Lines   MissedLines  Cover
18282      9734             46.76%    204983  97609        52.38%

full coverage report (for internal network access only)

@ti-chi-bot ti-chi-bot merged commit 677ad75 into pingcap:master Jun 3, 2022
@lidezhu lidezhu deleted the improve-bg-gc-interval branch June 3, 2022 01:16
ti-chi-bot pushed a commit to ti-chi-bot/tiflash that referenced this pull request Jun 3, 2022
@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #5062.

ti-chi-bot pushed a commit to ti-chi-bot/tiflash that referenced this pull request Jun 3, 2022
@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #5063.

@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #5064.

ti-chi-bot pushed a commit to ti-chi-bot/tiflash that referenced this pull request Jun 3, 2022
@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #5065.

ti-chi-bot pushed a commit to ti-chi-bot/tiflash that referenced this pull request Jun 3, 2022
@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #5066.

ti-chi-bot pushed a commit to ti-chi-bot/tiflash that referenced this pull request Jun 3, 2022
@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #5067.

@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #5068.

ti-chi-bot added a commit that referenced this pull request Jun 14, 2022
ti-chi-bot added a commit that referenced this pull request Jun 21, 2022
ti-chi-bot added a commit that referenced this pull request Jun 21, 2022
ti-chi-bot added a commit that referenced this pull request Jun 21, 2022
ti-chi-bot added a commit that referenced this pull request Jun 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-cherry-pick-release-5.0 PR which needs to be cherry-picked to release-5.0 needs-cherry-pick-release-5.1 PR which needs to be cherry-picked to release-5.1 needs-cherry-pick-release-5.2 PR which needs to be cherry-picked to release-5.2 needs-cherry-pick-release-5.3 Type: Need cherry pick to release-5.3 needs-cherry-pick-release-5.4 Should cherry pick this PR to release-5.4 branch. needs-cherry-pick-release-6.0 Type: Need cherry pick to release-6.0 needs-cherry-pick-release-6.1 Should cherry pick this PR to release-6.1 branch. release-note-none Denotes a PR that doesn't merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Background gc thread check interval is too short
5 participants