Optimization Opportunity: variable brotli quality level.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 13
- Forks
- 8
- Avg merge
- 3h 57m
- Merged PRs (30d)
- 7
Description
Currently the segmenter uses a configured fixed brotli quality level for all brotli operations within a run. We may be able to improve segmentation times without significantly impacting quality by using a variable brotli quality level based on the cost contribution of each patch. For patches that have have impact on total cost a higher quality level would be used, while patches with low cost impact could use a lower quality level (or even switch to estimating brotli compressed sizes).
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 tracing the segmenter’s Brotli operations and the configured fixed quality level used during a run. Determine how each patch’s contribution to total cost can guide quality selection or size estimation, then validate that segmentation time improves without significant quality impact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100