Assess Memory consumption in Pruner and share benchmarks
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6
- Forks
- 19
- Avg merge
- 12h 36m
- Merged PRs (30d)
- 27
Description
While the pruner was deployed in dogfooding cluster with deafult resource specs for controller, the pod faced 137(OOMKilled). After increasing the Memory Request to 512Mi and Memory limit to 2Gi the pod ran without any issues. Though there were no panics, this issue is created to analyze the performance of pruner and assess for any other possible issues.
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 reproducing the pruner's memory use with the default controller resource specs, then compare it with the 512Mi request and 2Gi limit configuration described in the issue. Collect memory benchmarks and inspect the controller's behavior for other resource-related problems; the work is done when the findings and any additional issues are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100