Optimization Opportunity: variable brotli quality level.
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- cpp
- Domain
- performance
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.
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).
- Dominant language
- C++
- Stars
- 13
- Forks
- 9
- Avg merge
- 14h 50m
- Merged PRs (30d)
- 6
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from w3c/ift-encoder
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
w3c/ift-encoder#271 ·
-
Consider adding a config setting that exempts high frequency codepoints from minimum group sizesOpen
Difficulty 5/5 Over a week Newbie friendliness 42/100
w3c/ift-encoder#269 ·
-
latest bazel does not workMay be free again @garretrieger claimed this 194 days ago, and no pull request is open. Open
w3c/ift-encoder#202 · 1 comment · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
w3c/ift-encoder#108 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
w3c/ift-encoder#105 · 4 comments ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
eclipse-score/inc_someip_gateway#356 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
HarperFast/rocksdb-js#945 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day