Skip to content

[Acceptors] Decouple Threadless pool setup/teardown from acceptor pool #706

@abhinavsingh

Description

@abhinavsingh

Is your feature request related to a problem? Please describe.
Currently, --num-workers is shared by both acceptors and threadless process pool. In a real world scenario, users may need to configure different number of acceptors vs threadless processes. Currently, there is a threadless process dedicated for each acceptor process.

Describe the solution you'd like

  1. Add a --num-acceptors flag
  2. Decouple threadless pool setup/teardown from acceptor pool class

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
This might be necessary if you are not expecting too many concurrent client requests but each request is a heavy request (e.g. file upload / file download).

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions