4 ms·
He didn't mention the biggest difference between gzip and xz - ram usage. At maximum compression, you need 674 MiB free to make a .xz file, and 65 MiB to decomp
by LeoPanthera 11y ago
He didn't mention the biggest difference between gzip and xz - ram usage. At maximum compression, you need 674 MiB free to make a .xz file, and 65 MiB to decompress it again. That's not much on most modern systems, but it's quite a lot on smaller embedded systems.
Admittedly, in most cases, that isn't much excuse though.
- gizmo 11y agoIt can also lead to disaster on a web server when linux decides to OOM kill a critical part of the infrastructure like the database server or memcached. Then you can get a cascading problem of services failing, all because of a careless unzip statement. (I've been there.)
- phaemon 11y agoYou can set exclusions for the OOM killer to prevent this. See: http://backdrift.org/oom-killer-how-to-create-oom-exclusions-in-linux http://backdrift.org/oom-killer-how-to-create-oom-exclusions...
- Spooky23 11y ago....or just use gzip and get 90% of the value minus the high probability that that setting will be fubar at an inconvenient time.
- deleted 11y ago[deleted]
- donatj 11y agoThis is why gzip rocks, the relatively low memory usage, in particular for compressing things on the fly.
- wtetzner 11y agoYeah, I use gzip for log processing tasks: zcat input.gz | log-processor | gzip > output.gz.