SMT max number loaded simultaneously
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3
- Forks
- 2
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 3
Description
Currently we just unload the engines after 10 minutes of inactivity - but we should likely offload them based upon memory availability or max number. This is a spin off of #338. We don't need to do anything now, because we just increased the RAM and are updating the GC settings. If it continues to be an issue (i.e., machine-engine crashes from out-of-memory), then we can update the algorithm (or increase RAM).
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
The issue names no files or tests. Start by locating the current engine-unloading logic that removes engines after 10 minutes, then read the context from issue #338 and review the RAM and GC assumptions. The issue is conditional and does not define a change or completion criteria until out-of-memory crashes continue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100