[IOTDB-6013] Pipe: pipe-related threads (pools) should not be initialized unless necessary #10229
+84
−46
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ized unless necessary
|
SonarCloud Quality Gate failed.
|
|
coverage: 44.489% (+0.01%) from 44.475% when pulling 036e16c on iotdb-6013 into 0bf7d75 on master. |
THUMarkLau
pushed a commit
that referenced
this pull request
Jun 20, 2023
…ized unless necessary (#10229) The number of resident threads has increased, which is not expected. There is an asynchronous client thread pool introduced to improve the performance limit of syncing data from Pipe to another iotdb instance, similar to the asynchronous client thread pool of IoTConsensus. It can be seen in the compute thread monitoring item. However, there is a problem that initialization should not be performed when it is not necessary.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The number of resident threads has increased, which is not expected.
There is an asynchronous client thread pool introduced to improve the performance limit of syncing data from Pipe to another iotdb instance, similar to the asynchronous client thread pool of IoTConsensus. It can be seen in the compute thread monitoring item. However, there is a problem that initialization should not be performed when it is not necessary.