I don't really need swap until I need to compile blender... Need somewhere around 64Gb (with compression) to deal with the peaks

Once tortured myself with having to go through...

The Android build system. Booo, scary.

I only wanted a LineageOS boot image built. The recommended specs list 64GiB RAM. Figured wouldn't apply to me until I tried to build a target literally called "nothing". It just used up all of the RAM and OOMed about 2 minutes in, building the "build cache" or whatever the fuck it needs to do to "warm up".

After a few fucktons of swapspace, turning off some of my daemons, some sysctl fuckery (there were options for limiting process virtual memory size IIRC? I put it all the way up) and taskset -p 0-15:1 (use logical CPUs 0, 2, 4...), I had my laptop allocating 50 something GiB. I have 16GB (decimal) physical RAM installed and I consider that already way too much for my usual needs.

After about half an hour of the build system build systeming, it just stopped doing that then built the kernel in 4 minutes with everything else in some time too.

Yes, I have tried just running make directly. That just resulted in an image that did nothing but toggle on and off an empty (no percentage) charging circle via power button.

Swap and zram saved my R and Python Dana analysis script a couple of times.

"I'm not a friggin bear, I don't hibernate!"

My built-in Devil's Advocate has to ask if that's really true? Have you got a citation newer than 2 decades old? Frankly, i find it difficult to believe that anyone wouldn't like to use electron software, for the simple reason that making your SSD suffer is fun.

Edit: in 30 years of administering Linux and (previously) Solaris sytems i've never once had to change HDDs or SSDs, so claims of torture are, i opine, exaggerated. i'll also claim that keeping electron software out of the filesystem is not good for your hygiene.

Everyone defending swap like crazy in the comments... so let me give a counter argument specifically for desktop:

Many years ago I stopped using swap on all my computers (I exclusively use linux) and the reason is: every time anything regarding interactivity went to swap, my system would freeze and literally become unusable for a really long time until I killed something. Since I got tired if that behaviour I decided I prefer for random shit to die but my computer still be usable.

It wasn't very often, but I don't get OOM killer often either (as in I don't remember the last time it happened and I use linux every day for both work and fun), and the freezing situation was way more annoying, to the point I sometimes ended up cold switching off the computer. I'm surprised on how many people run out of memory constantly. I guess you all are just using linux for servers and have crazy processing of infinite data...

swapfile gang

.rw------- root root 4.0 GB Mon Jun  1 04:10:37 2026  /var/swap

And here I am using swap for my self hosted services, some of which use ridiculous amount of ram.

Yes, swap partitions are shit.

The real hotness is swap drives.

Just the use that your old 64GB SSDs were waiting for!

(Fun fact: in Linux, if you have multiple swap partitions mounted, the kernel will automatically use striping (like RAID) in order to read and write from them as fast as possible. If you have multiple small SSDs used for swap, the read/write speed from swap can actually become pretty fast.)

> linuxmemes

> macos screenshot

ಠ_ಠ

I used to be this guy. We have huge amount of memory in our storage server. Why would we need swap? Well, once the system started killing programs I read up on swap and how the system handles its caches, especially ZFS ARC.

Short version is that while the system can evict its caches syncronously, it can only async notify ZFS that it should also shrink its caches, but the out-of-memory killer will start killing before ZFS and its kernel counterpart can start to free up memory.

A tiny bit of swap completely solved this, since swapping is sync for the kernel and the OOM killer will wait for it.

No

It turns out the computer mostly freezes once you go past 200% RAM used.

There are good use cases for swap. I work with very performance sensitive memory hogging applications that tend to process in bursts as incoming batched data arrives. We also have a lot of required background "security" applications.

Having the idle applications move out to swap so that a significant amount of free RAM to allow for the active, real-time applications to expand into is a major boon. RAM is expensive now, so it's become even more critical to not waste it.

But even in self-hosting at home I take advantage of it since I have a limited number of servers with limited RAM and a bunch of applications and/or docker containers running, many of which don't need to be active at all times, but if they were all active, would have trouble with the limited RAM. Swap allows for inactive applications to free up RAM for the active ones and leave enough available at all times to allow an application to quickly spin up new jobs.

Anyway, sure, for a simple desktop computer without a bunch of junk background applications running for "security" or whatever, and an overabundance of RAM installed, it's probably not useful. But for high performance, memory hungry applications with lots of background stuff running, it can be a big help.

That said, there are use cases where the opposite is useful and using a RAM drive is better than writing to disk for cache and temporary logs when you have enough RAM. My opnsense router for instance uses a RAM drive to store cache and logs (logs are mirrored to the NAS for long term storage, so just the local copy is lost on reboot). That system has enough RAM and I'd rather reduce disk wear, and I don't plan to add too many other applications to that server that it would run low.