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

Move to a common thread pool model #100

Open
AlexHarker opened this issue Apr 17, 2022 · 0 comments
Open

Move to a common thread pool model #100

AlexHarker opened this issue Apr 17, 2022 · 0 comments

Comments

@AlexHarker
Copy link
Owner

At the moment contexts own thread pools. That's very inefficient in cases where lots of contexts exist.

Reworking the processing queue to remove the thread pool (putting that in the global) and making use of it from there would be an optimal approach. This has a number of issues:

  • It becomes necessary to consider the number of items overall and per processing queue separately.
  • It becomes necessary to have threads servicing multiple queues

This issue might also help with the memory locking discussed in #81 as it opens up the possibility of thread-specific memory pools.

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

No branches or pull requests

1 participant