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

br: create database by db pool #50771

Merged
merged 2 commits into from
Feb 7, 2024

Conversation

Leavrth
Copy link
Contributor

@Leavrth Leavrth commented Jan 29, 2024

What problem does this PR solve?

Issue Number: close #50767

Problem Summary:
br restore is very slowly if there are many databases(2000+)

What changed and how does it work?

create database by db pool

Check List

Tests

  • Unit test
  • Integration test
  • Manual test (add detailed scripts or steps below)

40 minutes -> 5 minutes

  • 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

Signed-off-by: Leavrth <jianjun.liao@outlook.com>
@ti-chi-bot ti-chi-bot bot added release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jan 29, 2024
Copy link

tiprow bot commented Jan 29, 2024

Hi @Leavrth. 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.

Copy link

codecov bot commented Jan 29, 2024

Codecov Report

Merging #50771 (f123984) into master (761b404) will increase coverage by 5.6708%.
Report is 90 commits behind head on master.
The diff coverage is 52.0000%.

Additional details and impacted files
@@               Coverage Diff                @@
##             master     #50771        +/-   ##
================================================
+ Coverage   70.3318%   76.0027%   +5.6708%     
================================================
  Files          1456       1465         +9     
  Lines        420913     439267     +18354     
================================================
+ Hits         296036     333855     +37819     
+ Misses       104509      85194     -19315     
+ Partials      20368      20218       -150     
Flag Coverage Δ
integration 48.9781% <52.0000%> (?)
unit 70.3076% <52.0000%> (+<0.0001%) ⬆️

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

Components Coverage Δ
dumpling 54.0269% <ø> (ø)
parser ∅ <ø> (∅)
br 57.0589% <52.0000%> (+6.5154%) ⬆️

Copy link
Contributor

@3pointer 3pointer left a comment

Choose a reason for hiding this comment

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

LGTM

br/pkg/restore/client.go Outdated Show resolved Hide resolved
@ti-chi-bot ti-chi-bot bot added approved needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Feb 5, 2024
Co-authored-by: 3pointer <qdlc2010@gmail.com>
Copy link

ti-chi-bot bot commented Feb 7, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 3pointer, YuJuncen

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:

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 ti-chi-bot bot added lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Feb 7, 2024
Copy link

ti-chi-bot bot commented Feb 7, 2024

[LGTM Timeline notifier]

Timeline:

  • 2024-02-05 09:14:35.98905125 +0000 UTC m=+175401.555821127: ☑️ agreed by 3pointer.
  • 2024-02-07 02:36:03.993149034 +0000 UTC m=+324289.559918926: ☑️ agreed by YuJuncen.

@Leavrth Leavrth added needs-cherry-pick-release-6.5 Should cherry pick this PR to release-6.5 branch. needs-cherry-pick-release-7.1 Should cherry pick this PR to release-7.1 branch. needs-cherry-pick-release-7.5 Should cherry pick this PR to release-7.5 branch. labels Feb 7, 2024
@ti-chi-bot ti-chi-bot bot merged commit 3fab8fd into pingcap:master Feb 7, 2024
31 checks passed
@ti-chi-bot
Copy link
Member

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

@ti-chi-bot
Copy link
Member

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

@ti-chi-bot
Copy link
Member

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

ti-chi-bot bot pushed a commit that referenced this pull request Feb 9, 2024
ti-chi-bot bot pushed a commit that referenced this pull request Feb 27, 2024
@ti-chi-bot ti-chi-bot removed the needs-cherry-pick-release-6.5 Should cherry pick this PR to release-6.5 branch. label Mar 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved lgtm needs-cherry-pick-release-7.1 Should cherry pick this PR to release-7.1 branch. needs-cherry-pick-release-7.5 Should cherry pick this PR to release-7.5 branch. release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

br restore is very slowly if there are many databases(2000+)
4 participants