I was there man. I heard the constant HDD stuttering away. And it was a clear signal I had to go hunting for memory hogs.
If it happens in perfect silence and also doesn't slow your computer much then.. you wonder if some essential process is talking back and forth to the internet while your SSD wears down possibly for days on end?!?
A shame it's dead.
Fun days.
Now, we find out when the SSD wears out, in the worst case.
Not very long especially on modern consumer SSD. Depending on Drive size, at that speed we are talking about full drive write in ~5 to 10 min. On a 5-year warranty SSD that is about 1 - 2 weeks. We have tested Consumer SSD to last beyond their warranty. But even doubling that would only give you 2 - 4 weeks max.
Volatile memory that was significantly slower than RAM but could be parallelised to wide pipes for wide bandwidth.
Maybe just more flash to allow for more redundancy. Even if flash only lasted a week it's only two or three orders of magnitude to allow for practically usable lifetimes.
A rather amusing idea would be to have a box containing 1024 MicroSDs with a 512 byte block write. Wire them in parallel and you could do a swap drive with 512k blocks with rather impressive bandwidth. Setting them to actively use 0.1% of their data space and wear level across the whole thing they should last a fair few years at full usage. If you were treating them purely as swap you could tune your data size and consider the flash as a consumable. A quick google suggests that RAM is 100x flash, and that micro-SD and SSDs are roughly comparable now at price per bit. Maybe the sweet spot is around 10x redundancy in storage capacity. Then for the price of RAM you could get 10x that in swap with a really big pipe. 10x and cleverness might be ok (reads dominating in real world usage, even for swap, error correction might be able to squeeze quite a lot out with redundancy space.
I look forward to a crazy youtuber making one.
And even then: It doesn't reduce RAM use. Sync writes that are ultimately bound for spiny-rust-disk still reside in RAM (in TXG) until they lands on rust.
SLOG is thus mostly write-only in practice.
The performance boost is that it returns as soon a sync write successfully is recorded on the SLOG device (but before it lands on rust), which can improve performance for things that are limited by sync write speed.
On reboot or remount or whatever, SLOG gets reviewed and outstanding sync writes (if any) are permanently committed to the pool. That's really the only time it gets read.
---
Should a person play around with SLOG for performance? Yeah, sure, especially if they've got processes that are being held back by bursty sync writes.
Small-ish Optane devices are still available inexpensively, so as far as tweaky homelab computer tricks go in 2026: It's a cheap way to play with something new.
And small can be fine. It depends on the workload.
(Double-extra bonus point for using a redundant pair of them, though.)
Came back the next morning and was happy to find that the tests hadn't failed, unfortunately they had also gone far quicker than I had anticipated and had something silly like 2PB written.
Luckily the other half was more than plenty
Kidding/not kidding.
I've come to regard SSDs as ephemeral. I stripe-RAID them in my workstation to sum their speed as well as their failure rate. (Which actually also distributes the wear, so…)
And then I use the combined speed and terror to kindle the motivational fire of getting a proper backup solution underneath it.
Currently we run some datacenter SSDs which handle constant load just fine, despite being TLCs.
I believe they really put some magic smoke in these chips, because the endurance numbers are just black art at this point. Even my system SSD, which is an EVO860 256GB shows its wear level at 33% after 44K hours.
My /home disk, a 980 Pro 2TB, shows 1% wear after 835 hours. That machine is on 24/7.
Give it some time and you'll see numbers you believe was impossible to display on the output of uptime command. (:
If you want to check out whether your system has zswap enabled, you can look at /sys/module/zswap/parameters/enabled, which will be 0 if zswap isn't enabled and 1 or Y if it is. You can look at the kernel docs (<https://docs.kernel.org/admin-guide/mm/zswap.html>) for more.
I tried to summarise hows and whys here, in case it helps:
https://www.theregister.com/on-prem/2026/03/13/ram-is-gettin...
Apologies for the off-topicness?
—This is in earnest. The brain does operate according to information theory, certainly has memory, and does compress things.
Thus solving memory leaks forever...
Sure, they will get restarted, but not great.
So don’t change the OOM descision making, just the action taken.
I think the person below makes a good point though, that this encourages or permits buggy code.
If the oomkiller is running, it's too late to wait and see: some process or kernel thread needs memory that the kernel can't currently provide
Not how I expected the next big optimization push, but I'll take it.
... but reading say libraries directly and only putting in RAM the parts often used, now we're talking
Apparently though, tracking pages and access and stuff would be very slow.
I continued thinking about it on how to structure go or jvm apps that you split it in processes so they are more bound to when they are needed and you unload parts of your tool/programm by just handing over the results from one process to the other and kill it.
I have trouble thinking of a daemon this wouldn't break. It might break even a simple clipboard manager when you go back through the history.
Why not just change Linux's vm.overcommit_memory to not allow overcommitting, so that when a daemon/process does a malloc() an error is returned and it can be handled right away?
0: https://learn.microsoft.com/en-us/archive/msdn-magazine/2009...
a = “ha”
b = 10 * a
c = 10 * b
and so on and watching the memory climb in the activity viewer. I was surprised when the 10GB or even 100GB one (confirmed with len() ) didnt crash my 8GB laptop or even cause it to swap.Interestingly I tried the python version just now on modern macos, currently activity monitor shows 192GB ram used, 184GB compressed, on a machine with 36GB physical.
Actually something really weird happened, zsh killed the python proc, activity monitor shows it still alive, but the physical ram value is bugged and showing 0 bytes physical and 1.7 GB swap. So compressing RAM does have some limitations.
Apple's on-disk file compression is very mysterious, hard look up, and harder to intentionally trigger. The only clue in the Finder GUI is comparing the file size vs size on disk. Using the 3rd party `afsctool` you can tell APFS to compress a file on disk manually, but I believe there's no native macOS way to do this. The official way is that macOS decides for mysterious reasons when to compress a file on disk and it rarely does. But apparently generating a 100GB log file with million of repeated lines is enough to convince macOS to use APFS compression. (and having a disk that's nearly full probably)