Concurrent OpenAI-compatible API requests being handled sequentially
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.5k
- Forks
- 4.8k
- PR merge metrics
- No merged PRs in 30d
Description
Hi, thanks for your great work.
Recently, I've run CCU load tests with my local-deployed model and found that /v1/chat/completions API being handled sequentially although I've already set --limit-worker-concurrency when starting model_worker. What do you think is the problem here? Thanks!
Contributor guide
No contributing guide indexed for this repository
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
Start by tracing how model_worker handles concurrent requests to the /v1/chat/completions endpoint and how --limit-worker-concurrency is applied. Reproduce the reported behavior with a concurrent load test, then confirm that requests are no longer handled sequentially when the option is set.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100