Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dispatcher to use caller thread instead of dedicated scheduler thread #822

Merged
merged 1 commit into from
Jan 27, 2024

Conversation

pivovarit
Copy link
Owner

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:

  • helped avoid context propagation issues when execution switches
    between multiple threads
  • made the tool more Loom-friendly since instances of
    ParallelCollectors do not create their own threads

backport: c48c915

@pivovarit pivovarit merged commit ca27d4b into release/2.x Jan 27, 2024
@pivovarit pivovarit deleted the caller-thread-dispatcher branch January 27, 2024 07:41
pivovarit added a commit that referenced this pull request Jan 27, 2024
…#822)

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:
- helped avoid context propagation issues when execution switches
between multiple threads
- made the tool more Loom-friendly since instances of
`ParallelCollectors` do not create their own threads

----
backport:
c48c915
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant