-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[confighttp] Make the compression level configurable #10467
Comments
I like the idea of configuring this as a single string
|
Hi @mx-psi /@rnishtala-sumo , is this open for contribution? |
@wasim-nihal yes, please proceed if this issue is of interest to you. I can assist with the PR review. |
Assigned! |
The latest approach to configuring this is as follows
If the compression level is not set (0), then we use the default compression level (-1). This is consistent with the current behavior. cc: @dmitryax |
#### Description Add the option of configuring compression levels. This is not intended to be a breaking change for the user. #### Link to tracking issue Issue - #10467 #### Testing Unit tests were added/changed
Current compression algorithms seem to support multiple compression levels. These levels determine the speed and efficiency of the compression algorithm.
Lower compression levels provide faster speed but larger file sizes. Compression levels could be 3, 5, 7 or 11. Level 3 seems to be the default across multiple compression algorithms. It could benefit a user to give them the option to save on AWS egress costs by configuring a higher compression level with a tradeoff on processing speed.
Example configuration could looks like below:
The text was updated successfully, but these errors were encountered: