monitor child memory usage
Open
Nobody has claimed this yet.
feature-request
- Dominant language
- Ruby
- Stars
- 456
- Forks
- 149
- Avg merge
- 9d 7h
- Merged PRs (30d)
- 3
Description
monit style limits, e.g. 2 cycles at 500MB and QUIT, 6 cycles at 600MB and TERM, 8 cycles at 600MB and KILL.
must be settable in the config file (and the WebUI). must be settable per worker type, as well as for default.
will need to extend config file format to support this.
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
Start by tracing how the config file, WebUI settings, and child-worker lifecycle are handled. Define how per-worker-type and default memory limits interact, including the cycle thresholds and QUIT, TERM, and KILL actions. Done means the extended configuration and WebUI support all stated limits and apply them to child workers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100