[FEA] The CI should report size increase of `libcuvs.so` for each PR
Nobody has claimed this yet.
- Dominant language
- Cuda
- Stars
- 854
- Forks
- 236
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 62
Description
Is your feature request related to a problem? Please describe.
We want to keep a watch on the size increase of libcuvs.so. Right now there is no automated way of mesuring impact of a PR on the size.
Describe the solution you'd like
The CI scripts should measure and report the size increase in the report. One way to measure would be to have two builds: one with and one without the PR. Then compare the sizes of resulting builds. If there is an easier way to get the size from last successful build, that would be more efficient.
Describe alternatives you've considered
Additional context
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 locating the repository's CI scripts and the build steps that produce libcuvs.so. Determine whether a previous successful build can provide the comparison artifact or whether two builds are required, then define the CI report output and verify that each pull request shows the library size increase.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100