Dispatcher to use caller thread instead of dedicated scheduler thread #789
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
pivovarit
force-pushed
the
remove-thread-per-collector
branch
from
e9ef721
to
9fa3a22
Compare
pivovarit
force-pushed
the
remove-thread-per-collector
branch
14 times, most recently
from
d936a74
to
204e532
Compare
pivovarit
force-pushed
the
remove-thread-per-collector
branch
3 times, most recently
from
1976d8d
to
31700cc
Compare
pivovarit
force-pushed
the
remove-thread-per-collector
branch
from
31700cc
to
9f9b1f2
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.
Remove the internal single-thread scheduler and rely on the caller thread to submit all relevant tasks to a given thread pool. This not only simplified the solution, but also:
ParallelCollectorsdo not create their own threads