spinframework / spinframework/spin
Spin should block on accepting a request when at maximum concurrent instance limit
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 310
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 24
Description
Currently Spin returns an error "maximum concurrent instance limit of 1000 reached" when more than 1000 (by default) concurrent requests are made. Rather than failing, Spin should block new requests while waiting for instances to complete, providing backpressure.
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 payload names no file, test, or entry point; begin by locating Spin's request handling and the maximum concurrent instance limit. Completion means requests beyond the limit wait for an instance to finish instead of returning the quoted error, with coverage for that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100