spinframework / spinframework/spin
Component eviction / lazy loading
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 310
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 24
Description
This suggestion came from a discussion with a Spin user who had expected Spin to have a smaller memory footprint when the process is not servicing requests. They expected that the process would start listening for requests upon startup while not loading any components, as requests are received instances of the handling component would be created to handle them, then after a period of time the app would evict the components returning back to the svelte listening state.
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
No file, test, or entry point is named in the issue. Start by tracing Spin's startup, request handling, and component lifecycle, then clarify the design and acceptance criteria for listening without loaded components, creating instances on demand, and evicting them after inactivity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100