cache partition or namespace support
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Currently, all caches share the 10GB cache space. Once the 10GB limit is exceeded, caches are evicted in a random manner, which is problematic. Some “important” but small caches may be evicted by other “unimportant” but large caches.
I suggest implementing a cache namespace or partitioning mechanism, where the total size of all namespaces or partitions will still be 10GB, but cache removal will only happen within its own partition. In other words, the cache in partition A will only be evicted by the cache in partition A, and will not evict the cache in partition B or be evicted by the cache in partition B.
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 locating the cache storage and eviction entry points in the repository; no files or tests are named in the issue. Define how namespaces or partitions are represented and verify that eviction stays within a partition while the combined capacity remains 10GB.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100