-
Notifications
You must be signed in to change notification settings - Fork 66
Try to create tables in parallel #434
Comments
/pick-up |
This issue does not belong to any SIG. DetailsTip : Currently, we only support sig labels starting with Warning: None |
@kennytm shall we label it |
Could you please try pick up again? |
/pick-up |
This issue does not belong to any SIG. DetailsTip : Currently, we only support sig labels starting with Warning: None |
/cc @hi-rustin maybe later? |
This issue does not belong to any SIG. DetailsTip : Currently, we only support sig labels starting with Warning: None |
Try it when #498 megred. |
@hidehalo Please try again~ |
BTW, there's a similar issue in DM pingcap/dm#717 . We'll be happy if you could take a look after this one (will add learning material and score later) |
/pick-up |
Pick up success. |
Thx! |
@hidehalo You did not submit PR within 7 days, so give up automatically. |
/pick-up |
Pick up success. |
@hidehalo You did not submit PR within 7 days, so give up automatically. |
/pick-up |
Pick up success. |
@hidehalo You did not submit PR within 7 days, so give up automatically. |
/pick-up |
Pick up success. |
Feature Request
Is your feature request related to a problem? Please describe:
Currently we perform CREATE TABLE (
tidbMgr.InitSchema
) in sequence. But experiences in BR shows that running them in parallel is faster pingcap/br#377Describe the feature you'd like:
Execute the CREATE TABLE in
restoreSchema
in parallel over 16 connections.Benchmark that by importing 300 small tables.
Describe alternatives you've considered:
Don't do it.
Teachability, Documentation, Adoption, Optimization:
N/A
Score
600
SIG slack channel
sig-migrate
Mentor
@glorv @lance6716
The text was updated successfully, but these errors were encountered: