1. journalctl is painfully slow. Most frequent commands I use: journalctl -u myunit --since=today and journalctl -u myunit -n 1000 take minutes on loaded server

1. journalctl is painfully slow. Most frequent commands I use: journalctl -u myunit --since=today and journalctl -u myunit -n 1000 take minutes on loaded servers with large amount of logs. 1st command is instant for daily rotated plain text logs and 2nd is almost instant for any plain text logs. In theory it is possible to make a binary log database which will work fast for many queries including these, but journalctl is not fast at all. 2. People are fine with gzip because log compression is usually done in a way which makes log corruption/loss highly unlikely: gzip log.ystd, fsync log.ystd.gz, rm log.ystd At any time you can reset a server and you will either have uncompressed or compressed logs, not some partially written binary blob.