A recent GitHub issue highlights that systemd-journald can generate massive disk writes for single log lines, reaching 49KB on ext4 and over 110KB on btrfs. This behavior stems from filesystem-level overhead and journaling mechanisms rather than the log content itself. The finding suggests that high-frequency logging on these filesystems may cause unexpected I/O bottlenecks.
- Monitor disk I/O spikes if logging heavily on ext4 or btrfs.
- Consider xfs or zfs for high-throughput journaling workloads.
- Review log rotation and rate-limiting strategies to reduce write volume.
- Benchmark journald performance on your specific storage stack.