memorysafety / memorysafety/rav1d
Optimize memory usage
Open
Nobody has claimed this yet.
performance
- Dominant language
- Assembly
- Stars
- 643
- Forks
- 81
- PR merge metrics
- No merged PRs in 30d
Description
Currently our memory usage is larger than that of dav1d. We need to dig into why our memory usage is so much higher and optimize where possible. A possible cause is code size, which is tracked in #809.
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 profiling rav1d's memory usage against dav1d and review the code-size work tracked in issue #809 as a possible contributing factor. Done means the causes of the difference are identified and memory usage is measurably reduced where practical.
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
- 20/100