FileForums - Lzturbo: The fastest now more faster.

FileForums (https://fileforums.com/index.php)

- Conversion Tutorials (https://fileforums.com/forumdisplay.php?f=55)

- - Lzturbo: The fastest now more faster. (https://fileforums.com/showthread.php?t=99023)

Lzturbo: The fastest now more faster.

LzTurbo: The fastest now more faster
# New version :
- the fastest compressor now more faster.
- improved compression/decompression speed.
- improved compression. LzTurbo beats Lzma in compression with equivalent decompression speed.
- new TurboANX asymmetric numeral system w. JIT switching [scalar/SSE/AVX2].
Arithmetic coding rate at byte coding speed (see entropy coder benchmark http://encode.ru/threads/1890-Benchm...Entropy-Coders ).
Decoding speed [up to 1Gb/s] faster than most compressors with byte coding.
Can decompress 10 times and more faster than lzma with a bit less compression ratio
- Compression speed up to: 800 MB/s
and decompression speed up to 4 GB/s per core (tested on a 2600k cpu at 4.5 GHz)
- Standard input/output (stdin/stdout)
Download LzTurbo v1.2 for Windows and Linux at: http://sites.google.com/site/powturbo..
The only problem I am getting with lzturbo is, I am not able to use its <stdin> <stdout> function...
I checked it on a file of 312mb size...
pzlib+srep+lzma =121mb
pzlib+srep+zcm =110mb
pzlib+srep+lzturbo=107mb
pzlib+srep+nanozip=105mb...
decompression speed was way too better than lzma...
Please help if someone know how to use stdin stdout of lzturbo.

C Size ratio% C MB/s D MB/s Name
32798929 32.8 2.79 65.49 lzma 9
32922377 32.9 1.61 69.65 lzturbo 49

lzma wins, and i have notice that fazip's lzma is little bit fast and gets u even better compression
If u want to get do some real benchmarks with lzturbo
https://github.com/powturbo/TurboBench

@Prince: I only want to know best compressor... is lzma9 compatible with inno, I mean, does lzma 9 support stdin stdout, if yes can u give linkt to it...

Personally I would not change lzma with lzturbo, although the latter is a sufficiently valid compressor.

@felice... Although the creator mentions about lzturbo std stdout function,but it seems not working...
BTW, what switches can be used with lzma for better compression..

@ZakirAhmad ...ex "lzma:a1:mfbt4:d256m:fb128:mc1000:lc8"

Here a detailed explanation of the options to assistance to properly configure the compressor based on your requirements.

Code:

a=[0|1] : ( Defaul 1 ) : Sets compressing mode



a=[0|1] : Sets compression mode: 0 = fast, 1 = normal. Default value is 1.



mf={MF_ID} : ( Defaul 1 ) : Sets Match Finder



mf={MF_ID} : Sets Match Finder for LZMA. Default method is bt4. Algorithms from hc* group don't provide a good compression ratio, but they often work pretty fast in combination with fast mode (a=0). Memory requirements depend on dictionary size (parameter "d" in table below).

             

             MF_ID         Memory         Description

             bt2         d*9.5 + 4 MB         Binary Tree with 2 bytes hashing.

             bt3         d*11.5 + 4 MB         Binary Tree with 3 bytes hashing.

             bt4         d*11.5 + 4 MB         Binary Tree with 4 bytes hashing.

             hc4         d*7.5 + 4 MB         Hash Chain with 4 bytes hashing.



    Note: Your operation system also needs some amount of physical memory for internal purposes. So keep at least 32MB of physical memory unused.



d={Size}[b|k|m] : ( Defaul 24 )        : Sets Dictionary size



d={Size}[b|k|m] : Sets Dictionary size for LZMA. You must specify the size in bytes, kilobytes, or megabytes. The maximum value for dictionary size is 1 GB = 2^30 bytes. Default values for LZMA are 24 (16 MB) in normal mode, 25 (32 MB) in maximum mode (-mx=7) and 26 (64 MB) in ultra mode (-mx=9). If you do not specify any symbol from the set [b|k|m], the dictionary size will be calculated as DictionarySize = 2^Size bytes. For decompressing a file compressed by LZMA method with dictionary size N, you need about N bytes of memory (RAM) available.



fb={NumFastBytes} : ( Defaul 32 ) Sets number of Fast Bytes for Deflate encoder.



fb={NumFastBytes} : Sets the number of fast bytes for the Deflate/Deflate64 encoder. It can be in the range from 3 to 258 (257 for Deflate64). Usually, a big number gives a little bit better compression ratio and a slower compression process. A large fast bytes parameter can significantly increase the compression ratio for files which contain long identical sequences of bytes.



mc={N} : ( Defaul 32 ) : Sets Number of Cycles for Match Finder



mc={N} : Sets number of cycles (passes) for match finder. It can be in range from 0 to 1000000000. Default value is (16 + number_of_fast_bytes / 2) for BT* match finders and (8 + number_of_fast_bytes / 4) for HC4 match finder. If you specify mc=0, LZMA will use default value. Usually, a big number gives a little bit better compression ratio and slower compression process. For example, mf=HC4 and mc=10000 can provide almost the same compression ratio as mf=BT4.



lc={N} : ( Defaul 32 ): Sets number of Literal Context bits - [0, 8]



lc={N} : Sets the number of literal context bits (high bits of previous literal). It can be in range from 0 to 8. Default value is 3. Sometimes lc=4 gives gain for big files.

For me,lzturbo
eats a hugh amount of RAM at de/compression.
It has no percentage display
Afaik its source stolen from Bulat Z., author of Freearc....

Summa summarum,its based on Bulat's Tornado.
Its better if you stick with it. :) (supports stdin/out,decomp speed ~70-80 mB/s,with nearly LZMA ratio. :)

how to use stdin/out ?

TOR internally supported by ARC.EXE.

Or u can use externally TOR64.EXE,but cant tell you the parameters atm. (Im on mobile)

GOOGLE for it on encode.ru. there will be somewhere the parameters.
AFAIK laest tor64 is v0.6a.