ddl: ddl-owner try to use memory infoSchema to check first #10170
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
Make ddl-owner try to use memory infoschema to check first if the owner tidb-server already has loaded the latest schema.
Here is a simple test, There are 11394 tables in test20.
Deploy 1 tidb, 1 pd, 1 tikv.
create table
Before, spend 0.37s,
checkTableNotExists
spend 0.34sIn this PR: spend 0.07s,
checkTableNotExists
spend 267us.Create database
There are 18500 databases already in TiDB.
Before: spend 0.32S, and checkSchemaExist spend 250ms.
In this PR: 0.08s, checkSchemaExist spend 1 ms.
What is changed and how it works?
Change
checkTableNotExists
function.Check List
Tests
Code changes
Related changes