search

Freaky / Compactor

A user interface for Windows 10 filesystem compression
MIT License
1.16k stars 47 forks source link

Option to avoid LZX on large files #27

Closed Velocet closed 4 years ago

Velocet commented 4 years ago

Taken from LZX — new Windows 10 NTFS compression algorithm:

I strongly recommend avoiding LZX and using xpress16k instead.

The xpress algorithms do not require a full read of the file before performing operations, but can be done on the fly.

Thus, if you have a 1 GB file and you move it to another drive (say), with LZX your OS will sit at 0 until the whole thing is decompressed, and then it will eventually begin to start copying after sitting around for 30 seconds.

If you use xpress4k, xpress8k or xpress16k, the file will begin copying immediately.

And the compression improvement from xpress16k to lzx is always like 1.8 to 1.9, for example, it is not worth the overhead especially for large files.

I would suggest an option to use xpress16k on larger files even if LZX is choosen with a key to override it if really needed.

Freaky commented 4 years ago

This user is speaking nonsense as far as I can tell. LZX compressed files are split into independent 32k blocks, just as XPRESS compressed files are split into 4, 8, or 16k blocks - and they certainly don't behave as he describes in my tests.

Velocet commented 4 years ago

Thanks for your answer! I think this could be closed :)