Performance
Open
Nobody has claimed this yet.
Priority: Critical
- Dominant language
- C++
- Stars
- 9
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Some serious performance improvements are needed.
Steps:
- Seperate Tag matching and item finding
- Optimize both tag matching and item finding
- Implement cache to store recently used tag combinations (measurements needed to check performance)
Contributor guide
No contributing guide indexed for this repository
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 tag-matching and item-finding entry points in the C++ application and establish performance measurements for both paths. Done means the two operations are separated and optimized, with a cache for recently used tag combinations validated by measurements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100