-
Notifications
You must be signed in to change notification settings - Fork 131
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
zlib selection UI, compression levels, descriptions #145
Comments
hmm, it doesn't let the user select the compression level. |
To avoid having one more field, I just picked a few and set the compression level as well. Nobody complained so far. Of course there could also be a second dropdown to choose the level for each compression algo. Suggestion to choose the compression algo:
I we want to add the compression level instead of providing 3-4 default settings of algo + level, I'd just mark it as "good first issue". |
|
Then let's get to it. These are the available algos and standard levels:
First suggestion of combos:
I looked roughly at those tests: https://community.centminmod.com/threads/compression-comparison-benchmarks-zstd-vs-brotli-vs-pigz-vs-bzip2-vs-xz-etc.12764/ Thinking:
|
reverse order from fast to slow. that also moves borg's default lz4 compression to top of the list. |
OK. Then this wording and order, so users know the algo used.
|
Some users may have started their repo with zlib, so this should be offered also. Also noting that this is not a 1-dimensional thing, although a list might make it look like that. |
I know. One could write a master thesis about this topic. But many users will just want to pick something and forget about it. (added ZLib above) |
Is there a way to specify a custom compression level for an algorithm (zstd in my case)? |
You can add the command line option |
I just noticed that the UI for it is missing, it just offers all the others.
Also, I am not quite sure about the UI texts for the compression methods, my idea is rather:
The text was updated successfully, but these errors were encountered: