Quote:
Originally Posted by wrathma
wem(un)pak
|
Some small bug
Code:
Found 247 .wem files to pack (recursive)
Using 12 threads
[███████████████████████████████████████░] 246/247 (99.6%) ETA: 0s
All files packed successfully!
Also it would be good to give some information on how long the process took.
Another bug in decode mode
Code:
Found 389 .ww files to unpack (recursive)
Using 12 threads
[█████████████████████████████████████████████████░] 388/389 (99.7%)
All files unpacked successfully!
[██████████████████████████████████████████████████] 389/389 (100.0%)
Testing:
Surprised how fast this is compared to WemTool
Code:
input 339mb
output 316mb
wem-packer
encode 17sec
decode 5sec
wemtool
encode 50sec
decode 16sec
Both tools are running with all cpu threads.
Edit:
Impressive
Code:
input 5,12gb
output 4,82gb
wem-packer
encode 10m30s
decode 2m40s
wemtool
encode 30m20s
decode 13min
wempacker is 3x faster than wemtool
Suggestions:
Add -c option for hdiffz compression
Change skip -s option to skip files even if they are same size as input -> equal or greater then