On 19 Aug 2022, at 18:22, Adam Borowski <kilobyte@angband.pl> wrote:
Meow!
Because of the trimming changelogs discussion, I just wondered whether
it'd be beneficial to switch compression from .gz to .zst (gzip to zstd).
Numbers I got from the desktop I sit at:
* du of a copy of /usr/share/doc
366692
* rm ! -name "*.gz"
194184
* decompress
656852
* repack as zstd
163340
31MB saving, decent but not world shattering. Let's do so...?
But then, I looked at /var/log
* du
257612
* rm ! -name "*.gz"
53028
* decompress
471892
* repack as zstd
16360
Holy apt! Now this is a find! This box is a desktop thus doesn't produce
a lot of logs (just sbuild spam), but there's quite a few of my boxen where logs get very bulky.
Thus: let's switch logrotate from gzip to zstd? As changing the default would upset scripts, let's do it at the same time as enabling dateext...
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ You're alive. But that's just a phase. ⠈⠳⣄⠀⠀⠀⠀
I’d object that, because after we rotate the logs, we use a lot of z commands, namely zcat, zgrep, zless. Which allows us process many gigabytes of gzip files without extracting them first.
We have a big cluster at office and a central logging system. That system handles close to a thousand machines at the same time, and we neither have disk space, nor processing power problems.
Sorry for not agreeing with your idea, but operations needs this kind of interoperability and composability.
I’d object that, because after we rotate the logs, we use a lot of z commands, namely zcat, zgrep, zless. Which allows us process many
gigabytes of gzip files without extracting them first.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 339 |
Nodes: | 16 (2 / 14) |
Uptime: | 00:19:57 |
Calls: | 7,466 |
Calls today: | 2 |
Files: | 12,691 |
Messages: | 5,627,864 |