jnichols-git / jnichols-git/matcha
Optimization
Open
Nobody has claimed this yet.
help wanted
minor
- Dominant language
- Go
- Stars
- 9
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
A new version coming up is a great opportunity to take another look at performance. My local benchmark runs indicate we've lost some memory performance--would love to take a look at where that's happening and tie up loose ends. Will leave this open for contribution until we get close to releasing v1.3.0; please don't mark it as resolved if you contribute!
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 reported local benchmark and comparing memory performance with the current version. Identify where the regression occurs and document the benchmark result that shows the performance issue is resolved before v1.3.0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100