this is crush v1.3 based on v1.1 with amazing compression ratio improvements.![]()
this is crush v1.3 based on v1.1 with amazing compression ratio improvements.![]()
Amsal (13th January 2020),Entai44 (13th January 2020),RichSelian (29th January 2020)
you still have my thanks, great job
improve compression ratio for enwik9 file n decompression time is still fast![]()
Entai44 (15th January 2020)
do you know https://github.com/jibsen/bcrush ?
improve compression ratio from crush v1.0 size 279491430 bytes to 257210635 bytes (7.97%)
small file compression is worse.
very small improvements, but compression and decompression speed is very fast. decompression time for webster file only 1.17s. is it still pareto frontier ?![]()
An other test with enwik8 for bcrush
Speed is like 7.5KB/s. I looked into the code and i have to admit bcrush's code is very beautiful. The problem is that it uses hash chains which are very slow. It is better to use trees like other compressors.Code:30017634 bytes 221m18.11s real 220m57.49s user 0m11.91s system
EDIT: Also tested crush 1.7. Not compatible with original crush.
Last edited by algorithm; 19th January 2020 at 23:15.
jibz (20th January 2020),suryakandau@yahoo.co.id (20th January 2020)
-improve compression ratio
-compression time fast
- decompression time fast
![]()
this is the result of enwik8 using crush v1.9
compared with v1.3 and v1.6.test file is http://corpus.canterbury.ac.nz/resou...antrbry.tar.gz
alice29.txt 55671 57655
asyoulik.txt 51400 53759
cp.html 9124 9570
fields.c 3548 3829
lcet10.txt 137865 140757
plrabn12.txt 191857 196300
sum 14099 15244
xargs.1 2095 2266
may be bad offset. it is larger than current position.
suryakandau@yahoo.co.id (24th January 2020)