3 ms·
Here are the decompression timings: $ time ./6unpack /tmp/out.fastlz Archive: /tmp/out.fastlz alpha.txt [......................................
by ogrisel 14y ago
Here are the decompression timings:
$ time ./6unpack /tmp/out.fastlz
Archive: /tmp/out.fastlz
alpha.txt
[..................................................]
real 2m1.514s
user 0m12.038s
sys 0m16.199s
$ time ./LZ4Demo.exe -d /tmp/out.lz4 /tmp/out.lz4.txt
*** Compression CLI using LZ4 algorithm , by Yann Collet (Jul 25 2012) ***
Successfully decoded 3590403790 bytes
Done in 24.54 s ==> 139.53 MB/s
real 1m47.692s
user 0m6.320s
sys 0m18.227s
Decompression is thus faster for LZ4 but probably very limited in both cases by writing the output file to the SSD.
- ogrisel 14y agoIndeed for in-memory decompression LZ4 is much faster as expected: $ time ./LZ4Demo.exe -d /tmp/out.lz4 /dev/null *** Compression CLI using LZ4 algorithm , by Yann Collet (Jul 25 2012) *** Successfully decoded 3590403790 bytes Done in 8.04 s ==> 426.03 MB/s real 0m17.829s user 0m5.837s sys 0m2.206s I cannot do the same bench using fastlz default 6unpack program as it does not seem to be able to skip the filesystem based decompression.