Kaito
I'm so old school that in my mind, ssds are very fragile. I still have a habit of moving temporary directories off of the system disk to try to extend the life of the drive.
But the Samsung "Pro" series of drives have such insane wear capacity, and such excellent performance, that I don't think I have needed to worry about ssd wear for years. I should probably move all the temp directories back onto to the system drive.
Bernie
@kai for some workloads, the majority of I/O goes to /tmp and /var/tmp, so it makes sense to back them with the fastest possible filesystem and block device.
Usually, /tmp is an in-memory filesystem, like Linux's tmpfs, while /var/tmp is on persistent storage because... well, the original reason has been forgotten in UNIX's long history, but contemporary sysadmins think that it's either because large files could be written to /var/tmp, or because it it's used for checkpointing across crashes.
Bernie
@kai Shared temporary storage opens several security and resource management concerns.
If UNIX had filesystem namespaces from the start, they would have probably made /tmp a per-process or per-process group thing. And perhaps each user should have had its own $HOME/tmp.
Some programs honor TMPDIR, but many are just hard-coded to /tmp or /var/tmp, so you really need per-user mounts to make a private /tmp.
Bernie
@kai Oh, I forgot: nowadays, Linux *does* have a per-user tmpfs: it's mounted on /run/user/$UID/, and it has tighter limits than /tmp (1.6GB on my laptop).
Kaito
@codewiz ah, /tmp does share some ~8G filesystem with some other stuff and is not persistent across reboots.
Bobinas P4G is a social network. It runs on GNU social, version 2.0.1-beta0, available under the GNU Affero General Public License.
All Bobinas P4G content and data are available under the Creative Commons Attribution 3.0 license.