lance-format / lance-format/lance
Add RAM tests for file reader
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 7.1k
- Forks
- 852
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 272
Description
We should verify how much RAM the file reader uses in our unit testing. This will help ensure we don't introduce regressions when we make changes to the file reader. Primarily we should look at the size of the search cache after the file reader is initialized.
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
No file or test path is named. Start by locating the file reader initialization and its search cache, then identify the existing unit-test pattern for measuring memory. Done means tests verify RAM usage, especially search-cache size after initialization, and catch future regressions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- performance, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100