lance-format / lance-format/lance
Cache open fragments
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.1k
- Forks
- 852
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 272
Description
For every query, we call FileFragment::open(), which does maybe does some IO, schema manipulation, and then retrieves stuff from the metadata cache. Those first two will be optimized in #2420 and #2421. But if we are re-opening often enough for the same version of a dataset, it's perhaps worth considering caching these handles.
The main wrinkle is that these handles hold pointers to other data that is in the file metadata cache, which may pose issues for eviction policies (double counting size, evicting wrong items, etc.).
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 with FileFragment::open() and the metadata cache behavior described here, then review the related optimization work in #2420 and #2421. Define whether handles can be cached for repeated openings of the same dataset version while accounting for their pointers and cache eviction; done requires an agreed safe caching design.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100