3 ms·
Larger ramdisks :) With 64GB, I mount /tmp and ~/.cache as tmpfs, which speeds up web browsing and code compilation, but with more capacity I would mount /var
by imiric 3y ago
Larger ramdisks :)
With 64GB, I mount /tmp and ~/.cache as tmpfs, which speeds up web browsing and code compilation, but with more capacity I would mount /var or even / into RAM.
Granted, NVMe drives are so fast these days that the improvement of using RAM for storage is likely not noticeable. Plus there's the problem of persistence. If you're OK with volatile storage for your use case, then this won't be an issue. Otherwise, you need some way to ensure data is persisted.
Perhaps these RAM advancements will make hybrid DRAM/NAND drives cheaper and more performant.
- rbanffy 3y ago/var and / are odd choices (unless you are doing that for ephemeral containers), but in some setups I've done that with /var/log (mostly embedded SDCard machines with log shipping, where I'd prefer to avoid non-essential writes). When you do that it's good to set up some swap and start rotating logs as soon as you see swap usage. On environments with log shipping, having /var/log as a tmpfs makes a lot of sense.
- kobalsky 3y agoI use asd (anything sync daemon) and psd (profile sync daemon) to create ramdisk backed folders everywhere the neat thing is that these programs sync back periodically so the contents are preserved this gives you both the speed of ram, eventual persistence, and reduced wear down on ssds