mirror of
https://github.com/ckolivas/lrzip.git
synced 2026-04-04 22:07:42 +00:00
Deprecate the -M option as it is no longer of any significant utility compared to the -U option.
This commit is contained in:
parent
0f1d447541
commit
9c8b1ee795
7 changed files with 16 additions and 50 deletions
15
man/lrzip.1
15
man/lrzip.1
|
|
@ -55,7 +55,6 @@ Options affecting compression:
|
|||
\-z zpaq compression (best, extreme compression, extremely slow)
|
||||
Low level options:
|
||||
\-L level set lzma/bzip2/gzip compression level (1\-9, default 7)
|
||||
\-M Maximum window (all available ram)
|
||||
\-N value Set nice value to value (default 19)
|
||||
\-p value Set processor count to override number of threads
|
||||
\-T value Compression threshold with LZO test. (0 (nil) - 10 (high), default 1)
|
||||
|
|
@ -101,23 +100,15 @@ Set the compression level from 1 to 9. The default is to use level 7, which
|
|||
gives good all round compression. The compression level is also strongly related
|
||||
to how much memory lrzip uses. See the \-w option for details.
|
||||
.IP
|
||||
.IP "\fB-M \fP"
|
||||
Maximum window size\&. If this option is set, then lrzip tries to load the
|
||||
entire file into ram as one big compression window, and will reduce the size of
|
||||
the window until it does fit. This may induce a hefty swap load on your machine
|
||||
but can also give dramatic size advantages when your file is the size of your
|
||||
ram or larger.
|
||||
.IP
|
||||
.IP "\fB-U \fP"
|
||||
Unlimited window size\&. If this option is set, and the file being compressed
|
||||
does not fit into the available ram, lrzip will use a moving second buffer as a
|
||||
"sliding mmap" which emulates having infinite ram. This will provide the most
|
||||
possible compression in the first rzip stage which can improve the compression
|
||||
of ultra large files when they're bigger than the available ram. However it runs
|
||||
progressively slower the larger the difference between ram and the file size so
|
||||
it is worth trying the \-M option first to see if the whole file can be accessed
|
||||
in one pass, and then if not, it should be used together with the \-M option (if
|
||||
at all).
|
||||
progressively slower the larger the difference between ram and the file size,
|
||||
so is best reserved for when the smallest possible size is desired on a very
|
||||
large file, and the time taken is not important.
|
||||
.IP
|
||||
.IP "\fB-T 0\&.\&.10\fP"
|
||||
Sets the LZO compression threshold when testing a data chunk when slower
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue