memorysafety / memorysafety/rav1d
Investigate/optimize code size
Open
Nobody has claimed this yet.
performance
- Dominant language
- Assembly
- Stars
- 643
- Forks
- 81
- PR merge metrics
- No merged PRs in 30d
Description
Our code size is roughly 10x that of dav1d. We need to investigate why our code size is so much larger, and potentially optimize our code to generate a smaller binary.
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
The issue does not identify files, tests, build commands, or an entry point. Start by measuring the generated binary and comparing the project’s build configuration with dav1d; done would require identifying the main causes of the size difference and producing a smaller binary without regressions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100