mlcommons / mlcommons/endpoints
Max connections limits load concurrency
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 21
- Forks
- 28
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 13
Description
Observed that a single connection handles one request at a time and returns to the connection pool only after its request's response finishes.
This artificially limits the concurrency when it's greater than client's max connections.
Is this intended feature?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by tracing how requests acquire and release connections, then reproduce concurrency above the client's maximum connection count. Done requires establishing whether the behavior is intended and, if not, agreeing on the expected concurrency semantics and a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100