quickwit-oss / quickwit-oss/quickwit
Defaults concerning in-memory usage should reflect on available memory
Open
Nobody has claimed this yet.
backlog
enhancement
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
fast_field_cache_capacity, split_footer_cache_capacity and resources.heap_size have static values which may be larger than the memory available on the machine.
Ideally the defaults would not cause the user to run into memory issues.
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 definitions and initialization paths for fast_field_cache_capacity, split_footer_cache_capacity, and resources.heap_size. Check how available machine memory is exposed and whether tests cover these defaults. Done means the defaults scale with available memory without causing avoidable memory pressure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100