You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 20, 2023. It is now read-only.
Describe the feature you would like
I think we should use a thread pool with a fixed number of threads. There should be a queue where the threads of the thread pool get new requests from. When a new request comes in, it should be placed last onto the queue.
Is your feature request related to a problem? Please describe.
Right now, everytime when there is a new request, a new thread is created. That needs a lot of processing power and is very inefficient. In addition, there is no limit of concurrent threads yet. That means that if there are 200 requests at roughly the same time, 200 threads will be created.
Additional context
We have to keep the running time of every request very low. Otherwise, the next requests will be delayed too much.
The text was updated successfully, but these errors were encountered:
Describe the feature you would like
I think we should use a thread pool with a fixed number of threads. There should be a queue where the threads of the thread pool get new requests from. When a new request comes in, it should be placed last onto the queue.
Is your feature request related to a problem? Please describe.
Right now, everytime when there is a new request, a new thread is created. That needs a lot of processing power and is very inefficient. In addition, there is no limit of concurrent threads yet. That means that if there are 200 requests at roughly the same time, 200 threads will be created.
Additional context
We have to keep the running time of every request very low. Otherwise, the next requests will be delayed too much.
The text was updated successfully, but these errors were encountered: