Single log line is 49KB+ (ext4) / 110KB+ (btrfs) of systemd-journald disk writes(github.com)
253 points by ValdikSS 8 days ago | 218 comments
tl;dr: A bug report against systemd-journald 257.9 shows that a single ~200-byte log line triggers roughly 49KB of disk writes on ext4 and 110KB on btrfs, producing ~50 IOPS for just 2 log lines/second on a VM. The reporter argues this is measured after kernel write coalescing (ruling out the prior dismissal in issue #15292), and blames journald's inefficient on-disk format, which also bloats file sizes and has proven fragile across unclean reboots.
HN Discussion:
  • journald's design has drifted from its original intent of append-only efficiency
  • journald is broadly awful due to indiscriminate log spam and poor filtering
  • journald's indexing is slow and offers worse performance than plain-text tools like grep
  • Abandon systemd entirely in favor of alternative init systems
  • Technical curiosity about mmap writes and kernel-level details referenced in the bug report