Skip to content
This repository has been archived by the owner on Sep 20, 2023. It is now read-only.

Use a thread pool #38

Open
MaxiHuHe04 opened this issue Oct 13, 2019 · 0 comments
Open

Use a thread pool #38

MaxiHuHe04 opened this issue Oct 13, 2019 · 0 comments
Assignees
Labels
enhancement New feature or request
Projects

Comments

@MaxiHuHe04
Copy link
Member

MaxiHuHe04 commented Oct 13, 2019

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.

@MaxiHuHe04 MaxiHuHe04 self-assigned this Oct 13, 2019
@MaxiHuHe04 MaxiHuHe04 added the enhancement New feature or request label Oct 13, 2019
@MaxiHuHe04 MaxiHuHe04 added this to To do in development via automation Oct 13, 2019
@MaxiHuHe04 MaxiHuHe04 added this to the pre-alpha-2 milestone Oct 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
development
  
To do
Development

No branches or pull requests

1 participant