The relevant line from fstab is:
tmpfs /tmp tmpfs noatime 0 2
Now any program that writes to /tmp will be writing to a RAM disk, thus sparing unnecessary wear on my SSD.The relevant line from fstab is:
tmpfs /tmp tmpfs noatime 0 2
Now any program that writes to /tmp will be writing to a RAM disk, thus sparing unnecessary wear on my SSD.Swap on an SSD isn't even that slow.
This is not the case. RAM-based file system capacities are unrelated to process memory usage, of which "swap space" is for the latter.
Glad to help out. Here[0] is more information regarding Linux swap space as it relates to processes and the VMM subsystem.
> I stand by my original point, downvotes be damned.
:-D
I do not run systemd-based distros, so cannot relate.
Maybe some other ram disk things won't.
We are both wrong to a degree, but you are more correct than I was.
According to the docs[0]:
tmpfs ... is able to swap unneeded pages out to swap
space, if swap was enabled for the tmpfs mount.
So `tmpfs` does not unconditionally use swap, but can use it if possible. What I was thinking about is `ramfs`, which doesn't support swap, but that is not the topic of the question to which I replied.0 - https://www.kernel.org/doc/html/latest/filesystems/tmpfs.htm...
What I was thinking about is `ramfs`, which does not use/support swap and has other limitations not present in `tmpfs`.
Sorry for confusing the topic.
0 - https://www.kernel.org/doc/html/latest/filesystems/tmpfs.htm...
Honestly had no idea that was an option because I've never seen it disabled anywhere before.
> Honestly had no idea that was an option because I've never seen it disabled anywhere before.
Disabling swap is common with embedded systems, such as network gateways, routers, and other devices having no intrinsic mass storage devices.