quickwit-oss / quickwit-oss/quickwit
Readd compression on the Rest API output
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
In https://github.com/quickwit-oss/quickwit/issues/2958 we added compression for large output payloads.
We discovered however that compression was running on the tokio runtime, and harming Quickwit's performance considerably.
We should probably readd this compression but run it in the cpu intensive thread pool.
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 reviewing issue 2958 and the current REST API output handling to understand the previous compression work and where it was removed. Done means compression is restored for large responses while running in the CPU-intensive thread pool instead of the Tokio runtime, with the performance impact checked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100