Smarter Cache Management for tiflash-compute
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1k
- Forks
- 423
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 24
Description
Enhancement
Currently, TiFlash Compute caches data locally and only evicts entries when the cache reaches its capacity—using a LRU policy to remove the least frequently accessed items. However, TiFlash Compute lacks awareness of whether cached data has become obsolete—for example, due to compaction—meaning it cannot proactively identify and discard data that will never be accessed again.
As a result, a significant amount of useless or stale data may accumulate in the cache. When new data needs to be cached, the system must first evict older entries to make space, which can slow down the downloading and caching of new, relevant data.
Tasks
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 reading the linked issues 10619 and 10633 to understand the related cache-management work. The issue provides no files, tests, or entry points; completion would require defining and implementing proactive removal of obsolete cached data in TiFlash Compute.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100