The Unix zstd tool can compress using multiple threads. Number of threads can be specified with the -T flag and the -T0 flag will "attempt to detect and use the number of physical CPU cores" (from the man page).
I suggest having the option to enable zstd multithreading or perhaps making it the default in a fashion similar to the -T0 flag mentioned above.
In my experience, this makes a huge difference when using a high compression level. I just compressed 555MB of data using ouch c --slow and it took around 10 minutes. Then when using a similar maximum compression zstd command on the same data, it took about 30 seconds (sorry for not timing properly). Resulting file size was roughly the same, but I can't be certain how well I matched the settings used by Ouch's --slow flag.
A quick search of the zstd crate docs used by Ouch shows that it supports multithreading.
The Unix
zstdtool can compress using multiple threads. Number of threads can be specified with the-Tflag and the-T0flag will "attempt to detect and use the number of physical CPU cores" (from the man page).I suggest having the option to enable zstd multithreading or perhaps making it the default in a fashion similar to the
-T0flag mentioned above.In my experience, this makes a huge difference when using a high compression level. I just compressed 555MB of data using
ouch c --slowand it took around 10 minutes. Then when using a similar maximum compressionzstdcommand on the same data, it took about 30 seconds (sorry for not timing properly). Resulting file size was roughly the same, but I can't be certain how well I matched the settings used by Ouch's--slowflag.A quick search of the zstd crate docs used by Ouch shows that it supports multithreading.