br: more db pools to create databases

[Leavrth]

What problem does this PR solve?

Issue Number: close #56866

Problem Summary:
Currently, BR only has 16 db pools to create databases, and it takes about more than one hour to create 200K databases.

What changed and how does it work?

Use 100 db pools to create databases, and it only takes about half an hour to finish create 200K databases.

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

[tiprow]

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-sigs/prow repository.

[Leavrth]

/ok-to-test

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 57.5897%. Comparing base (3c8f2f3) to head (85ead57).
Report is 40 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #56867         +/-   ##
=================================================
- Coverage   73.3393%   57.5897%   -15.7496%     
=================================================
  Files          1636       1778        +142     
  Lines        453658     640011     +186353     
=================================================
+ Hits         332710     368581      +35871     
- Misses       100561     246926     +146365     
- Partials      20387      24504       +4117     

Flag	Coverage Δ
integration	38.9765% <ø> (?)
unit	73.2955% <ø> (+0.7438%)	⬆️

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

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

[princejha95]

Why we are only thinking till 200K databases ? Would this number can change in future ? If yes, we again have to make similar changes, right ?

[Leavrth]

Why we are only thinking till 200K databases ? Would this number can change in future ? If yes, we again have to make similar changes, right ?

hi, @princejha95 .
During the entire database creation process, the creation speed is basically constant. Therefore, the speed of creating databases does not depend on the number of databases to be created.
The purpose of increasing db pool size is to reduce the impact of one database creation DDL latency. The time it took to create the 200K databases is just one example. Based on this PR, we can infer that

+-----------------+-----------+
| databases count | time cost |
+-----------------+-----------+
| 200 K           | 30 min    |
+-----------------+-----------+
| 400 K           | 60 min    |
+-----------------+-----------+
| 600 K           | 90 min    |
+-----------------+-----------+
...

[ti-chi-bot]

[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:

• br/OWNERS [3pointer,YuJuncen]

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-28 07:40:30.276335806 +0000 UTC m=+249143.115491345: ☑️ agreed by YuJuncen.
• 2024-10-30 06:31:51.602129359 +0000 UTC m=+417824.441284902: ☑️ agreed by 3pointer.

[Leavrth]

/retest

[Leavrth]

/retest