EmbeddingGemma 2: an open, lightweight multimodal embedding model
deepmind.google·6d ago
AI Engineering
Hacker News·Aug 13·5 min read
Single log line is 49KB+ (ext4) / 110KB+ (btrfs) of systemd-journald disk writes
TL;DR
Systemd-journald is generating excessive disk writes, with log lines reaching over 49KB for ext4 and 110KB for btrfs. This issue mirrors a previously closed bug report, indicating a need for optimization.
✦ Why It Matters
Evaluate your logging configuration to minimize excessive disk writes and improve system performance.
Key Takeaways
- Monitor disk IOPS to identify performance bottlenecks.
- Consider alternative logging solutions to reduce disk write overhead.
- Test logging configurations in a VM environment before deployment.
- Stay updated on systemd-journald improvements and bug fixes.
Full Summary
The issue arises from systemd-journald, a logging service in Linux, which is writing log entries in an inefficient format. Users have reported that a single log line can exceed 49KB on ext4 and 110KB on btrfs, leading to around 50 input/output operations per second (IOPS) when only two log lines are generated per second.
This behavior was observed on Debian 13 with systemd version 257.9 and Linux kernel 6.12.57. The problem can be reproduced by running journald in a mode that writes logs to a hard drive while generating a constant stream of log entries.
Users have noted that the log files are not only large but also prone to corruption during unclean reboots, raising concerns about their reliability. This inefficiency can severely impact the performance of virtual machines, making it crucial for users to consider alternative logging solutions.