I get the idea behind it for sure but why use our available ram for this? I thought whatever init functionality would just wipe clean /tmp at boot.

Right now what I’m looking at is that if a system has 16gbram KDE Neon uses half of it for /tmp.

The thing is applications could output to /tmp for a plethora of reasons that could maximize that. Whether you are a content creator or processing data of some sort leaving trails in /tmp the least I want is my ram being used for this thing regardless.

Basically if you drop-in a 10GB file in /tmp right now (if your setup has tmpfs active) you will see a 10GB usage in your htop. Example in https://imgur.com/a/S9JIz9p

I’m not here to pick a fight but as a new KDE Neon user I’m scratching my head on the why after years in Arch Linux.

  • Strit@lemmy.linuxuserspace.show
    4·
    7 months ago

    2 good reasons to have your /tmp on tmpfs filesystems.

    1. It’s faster. RAM speeds are faster than your drive speeds, even SSDs.
    2. You are certain that all the files are removed on reboot, because RAM always gets cleared when it looses power.

    1 bad reason for having your /tmp be tmpfs.

    1. It can quickly fill out your RAM if your application (or you manually) drop huge files in /tmp and don’t move them out afterwards.

    In my mind, the Pros outweigh the Cons.