Closed indolering closed 3 years ago
turbobench.ini is only an example, you can make your own preferred settings.
If this is what you use for the headline results listed in the project's README, then leaving the defaults as-is misleads the reader.
I'll test and add your options for zstd when I make a new update the next time
Great! Looking over things again, I think I need to refactor my recommendations.
I'm not sure your intent for the TURBO/FAST/EFFICIENT/MAX/OPTIMAL categories are, but here is what settings I think match your intent while showing off the full range of ZSTD performance points:
--fast=7
now. I'm away from my Linux machine, but it looks like supplying an even higher number would be automatically fixed. You could supply 10
or 99
if you don't want to bother fixing it everytime ZSTD releases a new --fast
setting.--fast=1
, the default when passing just --fast
. Maybe level -1
as well?3
(the default) and 5
.22
preset in both MAX and OPTIMAL. 22
is a non-standard setting that third party decoders are allowed to reject because it can result in a DOS attack. It should still be included as it shows the maximum compression ZSTD can do, but probably not in both settings.... 19
is the universally compatible variant.--fast
settings as negative values.TL;DR: --fast=99/1
, -1/3/5/19
, and --ultra -22
Your default levels for ZSTD seem a little wonky:
-5
|--fast=5
(the fastest level currently available). This should push it into LZ4 territory.You might want to comment the .ini file, as it's not clear what each preset means (like BWT). Also, the README mentions includes a FASTEST preset the turbobench.ini file only has TURBO.