[PERF] The tag cache clears itself completely at 1,000 entries instead of evicting
Maintainers usually reply within 7 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
Research direction
Start by finding the in-memory tag cache used by the import decision maker and its 1,000-entry overflow handling. Check how tags are read and cached, then choose and implement an eviction policy such as LRU or oldest-first. Done means the cache evicts entries at capacity instead of clearing entirely; test with a folder larger than 1,000 entries and confirm tags are not repeatedly re-read.
Written by the indexing model from the issue text.
Description
Problem
The in-memory tag cache used by the import decision maker is capped at 1,000 entries and clears entirely when it overflows, so any folder larger than the cap thrashes it and re-reads tags. It should evict (LRU or oldest-first) instead. Low priority. Found while reviewing #220.
- Dominant language
- C#
- Stars
- 664
- Forks
- 48
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from Chaptarr/chaptarr
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 7 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Chaptarr/chaptarr#313 · 1 comment ·
Maintainers usually reply within 7 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 7 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 7 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 7 days
All issues in Chaptarr/chaptarr
Similar issues
-
python triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microsoft/semantic-kernel#14615 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
vzeol/DeployCraft#125 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
fboucher/2d6-dungeon-app#245 · 1 comment ·
Maintainers usually reply within 1 day
-
area: settings good first issue priority: p2 type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
AmineChr54/umbra#3 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day