We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The thread pool provides an easy way to have a well behaving JSON-RPC server in most situations, with some control of resources consumption.
The obvious issue here is the GIL which, depending on the server tasks, might prevent to gain as much parallelism as we would expect.
For that reason, it might be a good idea to implement a process-based pool, with a similar interface to the thread pool.
This won't work for servers keeping an internal state, but could increase performances for those communicating with backend servers.
You can vote for or against this issue.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The thread pool provides an easy way to have a well behaving JSON-RPC server in most situations, with some control of resources consumption.
The obvious issue here is the GIL which, depending on the server tasks, might prevent to gain as much parallelism as we would expect.
For that reason, it might be a good idea to implement a process-based pool, with a similar interface to the thread pool.
This won't work for servers keeping an internal state, but could increase performances for those communicating with backend servers.
You can vote for or against this issue.
The text was updated successfully, but these errors were encountered: