quickwit-oss / quickwit-oss/quickwit
The runtime as thread pool model for blocking task is leaving cpu off the table.
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
The merge task does a lot of IO. During that time we are wasting cpu.
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 merge task and the runtime thread-pool implementation, then inspect how blocking I/O is scheduled and measure CPU usage while the merge performs I/O. Done means the merge task no longer leaves available CPU unused during those waits, with behavior and performance verified by the relevant existing checks or benchmarks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100