datafusion-contrib / datafusion-contrib/liquid-cache
Support a RAM-only mode (no disk spill)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 452
- Forks
- 51
- Avg merge
- 3h 10m
- Merged PRs (30d)
- 12
Description
A way to run LiquidCache as a pure in-memory cache — stay in RAM up to the configured budget, drop the LRU tail when full, and never write to disk — would be useful. Some deployments don't have fast scratch disk, or want predictable RSS without surprise I/O latency, and in those cases re-fetching from the upstream source on a miss is preferable to spilling and rehydrating.
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 LiquidCache's cache configuration and its existing disk-spill, rehydration, and eviction paths, then review related tests. Done means a configurable RAM-only mode stays within the memory budget, evicts the LRU tail when full, performs no disk I/O, and refetches upstream data on misses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100