Open tcalmant opened 5 years ago
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 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.