5 comments

  • barrkel9 minutes ago
    journald is IMO the worst part of the systemd ecosystem. You're better off using it only as a router and not storing any logs in it. The indexing system it uses is slow and provides no control over chatty subsystems - you cannot truncate the logs for just a single identifier. For all the use indexing is doing you will get better performance out of a modern grep like ag or rg. Structure is worth something but it's better off somewhere other than journald.
  • amluto11 minutes ago
    Ooh, mmapped writes. I make that mistake once, years ago. :) I posted a comment in that GH issue.
  • smartmic34 minutes ago
    I recently looked into disk usage of journald and was also shocked. My next step towards peace of mind is <a href="https:&#x2F;&#x2F;www.devuan.org&#x2F;os&#x2F;init-freedom" rel="nofollow">https:&#x2F;&#x2F;www.devuan.org&#x2F;os&#x2F;init-freedom</a><p>Will try it out as next distro for my Debian system, longtime experience with Void Linux (runit) on another box is great.
    • ValdikSS27 minutes ago
      Many applications hammer the disk even if the developers don&#x27;t believe this is an issue, not only journald, unfortunately.<p>It&#x27;s my third attempt to make my regular Linux desktop less disk-chatty. This is a huge issue for btrfs and for COW FS in general, because they have massive write amplification for small and frequent writes (38,7 TB written to my idle desktop SSD in 2 years).<p>If you&#x27;re interested, here are my findings this time so far:<p><pre><code> - workrave: 60 second stat sync https:&#x2F;&#x2F;github.com&#x2F;rcaelers&#x2F;workrave&#x2F;pull&#x2F;717 - kde klipper: saves to disk on every copy, even if permanent storage is disabled https:&#x2F;&#x2F;bugs.kde.org&#x2F;show_bug.cgi?id=501030 - kde plasmashell: saves qt shader cache each time notification popup disappears https:&#x2F;&#x2F;bugs.kde.org&#x2F;show_bug.cgi?id=523805 - bitwarden firefox extension: tries to connect to desktop application every 10 seconds, writes about every failure to browser&#x27;s WebStorage 14+ KB https:&#x2F;&#x2F;github.com&#x2F;bitwarden&#x2F;clients&#x2F;issues&#x2F;22192 - firefox datareporting&#x2F;glean: very chatty .mozilla&#x2F;firefox&#x2F;xxx&#x2F;datareporting&#x2F;glean&#x2F;db&#x2F;data.safe - ipfs: writes every received DHT announce to disk, 20 GB in 3 hours https:&#x2F;&#x2F;discuss.ipfs.tech&#x2F;t&#x2F;constant-writes-to-datastore-log&#x2F;20316 - mailcow: redis saves data every 5 minutes https:&#x2F;&#x2F;github.com&#x2F;mailcow&#x2F;mailcow-dockerized&#x2F;pull&#x2F;7405</code></pre>
      • doublepg234 minutes ago
        The two I most often see in Ubuntu&#x27;s dmesg are:<p>audit - appears to be some sort of AppArmor logging?<p>br[] - bridge interface docker uses consistently rebuilds itself? May be related to docker compose networking.
    • p_l10 minutes ago
      systemd-journald has one of the most deranged log file formats I have ever dealt with, and one of the worse user interfaces, too.<p>I am not again binary logs, or logs in a database. It&#x27;s just yet another time I deal with good ideas implemented horribly, horribly badly when it comes to systemd.
  • ValdikSS56 minutes ago
    <a href="https:&#x2F;&#x2F;github.com&#x2F;systemd&#x2F;systemd&#x2F;issues&#x2F;40262#issuecomment-5169482357" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;systemd&#x2F;systemd&#x2F;issues&#x2F;40262#issuecomment...</a>
  • tryauuum13 minutes ago
    hello ValdikSS! nice to see you alive