Define minimum container specs — memory requirements for smooth experience
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 1
- Avg merge
- 7h 13m
- Merged PRs (30d)
- 31
Description
Claude Code sessions are memory-hungry (~500MB-1GB each active session). We need documented minimum specs and ideally a way to enforce/warn.
Current state
- Each Claude session: ~500MB-1GB RSS
- 8 accumulated zombie sessions → 3.2GB RSS, swap full, OOM crashes
- Default container has no memory floor defined
Needed
- Benchmark: measure memory per session type (beaver, raccoon, otter, dog)
- Define minimum specs: RAM, CPU, disk for smooth operation (1 active session, 3 concurrent, etc.)
- Document in README and onboarding
- Woltspace doctor (#105) should warn when below minimums
- Consider increasing default Docker memory allocation
Related
- #129 (OOM crash + zombie accumulation)
- #105 (woltspace doctor)
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 benchmarking memory use for the beaver, raccoon, otter, and dog session types across the requested concurrency levels. Then review the README, onboarding material, and the woltspace doctor work in #105; done means minimum RAM, CPU, and disk requirements are documented and low-resource environments can be warned about. Use #129 for the related OOM and zombie-session context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- documentation, infrastructure, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100