Add a memory usage check
Open
Nobody has claimed this yet.
chore
- Dominant language
- Ruby
- Stars
- 10k
- Forks
- 1.2k
- Avg merge
- 14h 38m
- Merged PRs (30d)
- 92
Description
Coming from #2440 and #2441 and similar leaks that we've had in the past, add a tool that compares memory usage before/after a change in pull requests. This could be modeled after https://code.dblock.org/2024/04/19/commenting-on-pull-requests-in-github-actions.html (newer version in https://github.com/opensearch-project/opensearch-api-specification/pull/297).
- Create a benchmark that causes a lot of memory allocations quickly.
- In every PR run the benchmark on the before code and the after code, generate some data on allocations.
- Add a comment to the PR showing the change.
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 reviewing the linked GitHub Actions examples and the related issues #2440 and #2441. Create a benchmark with rapid memory allocations, run it against the before and after code for every pull request, and verify that the pull request comment reports allocation changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, ruby
- Domain
- ci-cd, devops, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100