CompactGUI VS lzbench

CompactGUI

Also, check out CompactGUI. It's a more user-friendly and efficient way of using Windows' built-in compression to cut the game's file size almost in half. It makes load times marginally longer (like 5-10%) and needs to be redone every few updates to keep the size down, but it works.

You can chuck compact.exe at it by hand (use the /exe option), or if you'd prefer to avoid the command line there's my Compactor tool, or the venerable CompactGUI.

You can also just use compactGui smaller filesizes without having to remove dialogs or cutscenes or anything. Obviously how much space is regained depends on how well it was compressed originally. With triple A titles perhaps getting 10% back, while things like ark can literally be shrunk by hundreds of gigs.

Not really related to your question but if you want to try and save some space you can give this a go, I've used it before and never had any issues. https://github.com/IridiumIO/CompactGUI

Meet you new best friend. https://github.com/IridiumIO/CompactGUI

For a benchmark on a standard set: https://github.com/inikep/lzbench/blob/master/lzbench18_sort...

Do not re-compress your file into level 3. The decompression speed is largely the same between level 3 and 8, so you just wasting CPU doing nothing and making your files larger. See the bottom of the README: https://github.com/inikep/lzbench

You can crunch the numbers yourself with this: https://github.com/inikep/lzbench

Note that a benchmark in the README refers to zstd 1.1.1 and brotli 0.5.2, which are very old (the current versions are zstd 1.5.2 and brotli 1.0.9). The same author maintains lzbench [1], which is more or less up-to-date.

[1] https://github.com/inikep/lzbench

u/zertillon, maybe you could use lzbench, so you could compare it with a lot of other compression libraries. The problem is that it requires including the library in a single executable, so it might be more difficult to integrate than a C library (the benchmark is in C++).

Still updated: https://github.com/inikep/lzbench

If you want to know the size a VM will compress to,. Zstd can be installed on any machine, so you can experiment easily. You can even run the benchmark https://github.com/inikep/lzbench

Are you sure about that? That's not what I see on https://github.com/inikep/lzbench and I tried to run that myself, although I have no idea which lzo to try so I went with what seemed the fastest...