As a normal, boring user that does nothing special other than browse the internet and the occasional "casual coding" -- what am I supposed to do with 32GiB of ram?
Title. Besides setting tmpfs to use 10GiB of it to store downloads.
Just open a few more Chrome tabs: a couple of Ali Express and Amazon pages and a few YouTube videos and couple Reddit posts, and you’ll be wondering why you only got 32.
you can disable paging (swap) i guess apart from launching more things at the same time and letting apps know you have ram for them to cache shit (check app settings some apps do have a how much ram should we use slider like okular the kde pdf viewer) and virtualisation of multiple os’s i can’t think of much
Nothing, there is no reason to put that much RAM on your system if you don’t even know what to do with it. “What is someone who only uses his car to commute supposed to do with a supercar?”
A supercar is like having a fast CPU. I still want it so I can go zoom zoom. Having more RAM is like having more seats in your car. Pointless most of the time but occasionally very useful.
Only two things. Rust is 12 gigs on disk(which translates into 12 gigs of ram if you use tmpfs) and IDK how much in ram. Chromium is about same. Keep rest of ram for linker.
LSPs, linters, AI auto complete, multiple ranked auto complete sources, contextual syntax highlighting abused to feed things like symbol tree views, type analysis, scoped file trees depending on what you’re working on, infinite undo since last commit, and all available in real-time.
I feel like I use up 8GB the moment I type “neovim” on a sufficiently large node project, lol.
Run different virtual machines for different purposes. For example, you can have a VM that does all its networking over a VPN and downloads torrents in the background while you do other things. Or you can run other OSs in VMs.
Also, containerized software is everywhere now and it uses more resources. Extra memory helps.
I don’t think you need 32GB of RAM. 16GB should be enough, and 8 will still do for light tasks (though modern apps and websites are starting to push that, which is terrible). Your OS uses any RAM you don’t use to cache files, which speeds up your system, reduces power consumption, and could save you some SSD wear by caching the writes.
If you haven’t already, you can mount a tmpfs over your browsers’ cache directories (a bunch of them in ~/.cache or ~/. config). It used to really speed up browsing back in the HDD days. I doubt it’s still necessary, but hey you’ve got plenty of RAM, right?
If you really don’t do anything but browsing, you could boot your entire OS into RAM and have a 0 SSD latency browsing experience.
You could also use the RAM to run a bunch of VMs or containers. I used to run a separate Pihole VM, for example; virtual machines are nice and isolated, so you don’t risk ruining your /etc directory with a billion different configured services. The big downside of running such stuff on your machine is that you quickly end up with a whole bunch of duplicates (I have like four versions of postgres running on a server somewhere because I’m lazy) but if you have RAM to spare, that doesn’t matter.
One container that may be worth looking at is Waydroid (or Anbox if you’re on X11) to run Android apps on your desktop. I find that a bunch of different services have web interfaces thst just don’t work as well as their apps, and running those can be nice. How much of a difference this makes will depend on the services you use, of course.
Lastly: don’t underestimate the advantages of plenty of RAM when programming. It’ll depend on what language you use, but many compilers will generate a million tiny files that will all be written to disk and read back. SSDs are fast, but random reads are still nowhere close to RAM speed. Your OS will hide most of this overhead, but I definitely felt the difference going from 16GB to 32GB because of file system caching alone.
Add comment