[WIP]ddl: modify param at runtime for add-index on DXF local sort

[D3Hunter]

What problem does this PR solve?

Issue Number: ref #57497, ref #57229

Problem Summary:

What changed and how does it work?

Check List

Tests

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

  • ENV: 1pd/1tidb/1tikv

  • create table t(id bigint primary key auto_increment, b varchar(1024), c varchar(1024)); and insert 16M rows

  • run alter table t add index(b(128));, the total index KV is about 5G

  • case 1: with initial thread=2/batch_size=32, after admin alter ddl jobs 131 thread = 8, batch_size = 256;, time of encoding part changes from 34s -> 18s

  • case 2: with initial thread=4/batch_size=256, after admin alter ddl jobs 133 thread = 1, batch_size = 32;, time of encoding part changes from 16s -> 28s
    

  • case 3: with initial thread=4/batch_size=256/max_write_speed=100M, after admin alter ddl jobs 135 max_write_speed = 0;, time of importing part changes from 53s -> 23s

  • case 4: with initial thread=4/batch_size=256/max_write_speed=200M, after admin alter ddl jobs 137 max_write_speed = '100M';, time of importing part changes from 26s -> 49s

• 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

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from d3hunter, ensuring that each of them provides their approval before proceeding. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS
• pkg/ddl/OWNERS
• pkg/disttask/OWNERS
• pkg/meta/OWNERS
• pkg/resourcemanager/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tiprow]

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

[codecov]

Codecov Report

Attention: Patch coverage is 68.01471% with 87 lines in your changes missing coverage. Please review.

Project coverage is 74.9115%. Comparing base (444c38f) to head (e2b3030).
Report is 17 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #59343        +/-   ##
================================================
+ Coverage   73.0574%   74.9115%   +1.8541%     
================================================
  Files          1689       1737        +48     
  Lines        466990     476610      +9620     
================================================
+ Hits         341171     357036     +15865     
+ Misses       104844      97106      -7738     
- Partials      20975      22468      +1493     

Flag	Coverage Δ
integration	48.8172% <6.8085%> (?)
unit	72.2806% <68.0147%> (+0.0225%)	⬆️

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

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	61.0509% <ø> (+15.6423%)	⬆️