feat[consumer]: support custom thread pool, providing the possibility for different consumers to reuse thread pools #8994
+131
−32
Conversation
This file contains 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
… for different consumers to reuse thread pools
AuroraTwinkle
force-pushed
the
feat/supportCommonConsumeExecutor
branch
from
48a755a
to
9b6f373
Compare
AuroraTwinkle
force-pushed
the
feat/supportCommonConsumeExecutor
branch
from
b5a3d9b
to
7b2128e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Which Issue(s) This PR Fixes
Fixes #issue_id
In our scenario, there is a centralized message proxy service,this service will create a lot of consumer groups to consume many topics and cache messages locally.Then the business will pull messages from the cache of the proxy service.
In some scenarios, tens of thousands of consumers may be started in one instance, and the traffic of most consumers is very low or even non-existent. These consumers each have their own independent thread pool, causing the JVM to create tens of thousands of threads, seriously affecting performance.
Therefore, I have an idea. Can we allow different consumers to reuse the thread pool for this scenario, reduce system resource consumption and improve performance?
Brief Description
How Did You Test This Change?