// HACKER NEWS — CYBERSECURITY
Single log line is 49KB+ (ext4) / 110KB+ (btrfs) of systemd-journald disk writes
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Log writes should be within order of magnitude of syslog
VM doing ~50 IOPS when writing 2 lines of log per second
this is exactly same issue #15292 that was closed without good reason
Step 1. Use journald in mode where it writes to hard drive. The FS is XFS
Step 2. have constant stream of log entries going on a VM
I used VM as example because the complaint in #15292 was "iotop is not accurate" (I can believe that, it's before any OS write coaelscing) but this clearly shows traffic after every kernel mechanism was used. So no, it isn't "kernel making lotsa iops out of it", it's slow.
Journald just uses extremely inefficient format (also I've seen it corrupt on unclean reboot enough times to declare it's not even all that resilient) as files are also multiple times the size of what's actually written in them.