4 ms·
If you're really that sensitive to size, may want to try 7z. I can usually get a few % smaller archive sizes than xz with faster decompression to boot. Of cours
by eyegor 5y ago
If you're really that sensitive to size, may want to try 7z. I can usually get a few % smaller archive sizes than xz with faster decompression to boot. Of course then you might need to install a 7z lib which could be an issue.
- latchkey 5y agoThanks, I just tested that idea out: Input binary size: 12996608 Folder contains a few more bytes for the service file and installer script. 4476005 (gz) 3421456 (xz) 3447940 (7Z) tar c -C ./build $(BINARY) | gzip -9 - > $(PKG_NAME_GZ) tar c -C ./build $(BINARY) | xz -z -9e - > $(PKG_NAME_XZ) tar c -C ./build $(BINARY) | 7z a -si $(PKG_NAME_7Z) I played around with the compression options on xz. If you have some suggestions on improving 7z, I'm all ears. Decompression time isn't an issue here. Installing 7z on the hosts isn't great, but could be done.
- eyegor 5y agoYou could try the compression options for 7z, not sure if they would help in your case since I don't know the defaults off hand. Here's an example from the man page. > ... | 7z a -si -m0=lzma -mx=9 -mfb=64 -md=32m https://linux.die.net/man/1/7za https://linux.die.net/man/1/7za
- latchkey 5y agoThanks again. Using those exact options. 3421498 (7z) 3420832 (xz) Wild that xz is not the same every time.