ckolivas/lrzip
1
0
Fork 0
mirror of https://github.com/ckolivas/lrzip.git synced 2026-01-16 21:39:57 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update README.

Browse source
This commit is contained in:
Con Kolivas 2010-11-16 23:23:28 +11:00
parent 0a4f6807e5
commit 81ac86856b
1 changed files with 8 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
README
View file

@ -210,14 +210,13 @@ the only compression format that can do any significant compression of
multimedia.
Q. Is this multithreaded?
A. As of version 0.530, it is HEAVILY multithreaded with the back end
compression phase, and will continue to process the rzip pre-processing phase
so when using one of the more CPU intensive backend compressions like lzma or
zpaq, SMP machines will show massive speed improvements. Lrzip will detect the
number of CPUs to use, but it can be overridden with the -p option if the
slightly better compression is desired more than speed. Decompression at the
moment is not multithreaded, but is already much faster than the compression
phase (except for zpaq), but enhancements for decompression are planned.
A. As of version 0.540, it is HEAVILY multithreaded with the back end
compression and decompression phase, and will continue to process the rzip
pre-processing phase so when using one of the more CPU intensive backend
compressions like lzma or zpaq, SMP machines will show massive speed
improvements. Lrzip will detect the number of CPUs to use, but it can be
overridden with the -p option if the slightly better compression is desired more
than speed.
Q. This uses heaps of memory, can I make it use less?
A. Well you can by setting -w to the lowest value (1) but the huge use of
@ -361,7 +360,7 @@ Ed Avis for various fixes. Thanks to Matt Mahoney for zpaq code. Thanks to
Jukka Laurila for Darwin support. Thanks to George Makrydakis for lrztar.
Con Kolivas <kernel@kolivas.org>
Mon, 7 Nov 2010
Mon, 16 Nov 2010
Also documented by
Peter Hyman <pete@peterhyman.com>