Do not buy RAM, compress (curiousbits.nl)
157 points by Ecno92 10 hours ago | 135 comments

• varenc 3 hours ago

As others have said, macOS does this by default and it's quite impressive. I have a long running daemon with a memory leak. By its nature, the leaking memory is very repetitive and easily compressed. Right now this daemon has tried to claim 2.5GB of memory, but it's been compressed to a mere 450MB of actual memory! And because it's a memory leak, it never accesses this old stuff, so it never gets decompressed. Only 20MB of RAM is held that isn't compressed.

Of course, it would be far better to just not have the memory leak...but in the mean time, macOS memory compression is making the leak nearly a none issue.

• cpeterso an hour ago

A new take on the OOM killer: if a long-running daemon hasn't touched some heap pages for a very long time, perhaps the OS could assume it is leaked and unmap the pages. If the daemon tries to access that memory, let it crash.

• kevincox 37 minutes ago

This sounds like a bad idea. No one has logged in via SSH for a while so the daemon hasn't touched any pages (or only pre-auth relevant pages) then when you log in it gets killed. Or if someone sends a rarely used request to an HTTP server then it crashes accessing some data unique to that request.

Sure, they will get restarted, but not great.

• dotancohen 27 minutes ago

Or swap it to a less expensive medium, such as the SSD.

• TheSoftwareGuy 21 minutes ago

That’s actually a very old idea, called paging or swapping. And it totally works

• davidkwast 2 hours ago

It's like having a room that shrinks everything to 1/5th of its size but you never come back to get anything. It will work until gets full.

• 01HNNWZ0MV43FF an hour ago

If the user was feeling stochastic, the OS could theoretically just drop pages that haven't been accessed in, say, 2 days, and send the process a segfault if it tries to access them.

Thus solving memory leaks forever...

• bayindirh an hour ago

I believe one can create a kernel module called leaky_ram to make this possible. No?

• trollbridge 3 hours ago

Wait until people find out about swapping.

• bayindirh an hour ago

Oh we found out about it. In the old days, a machine with a load of 57380 (probably not the highest number I have seen) means the machine has run out of memory and started swapping heavily.

Fun days.

Now, we find out when the SSD wears out, in the worst case.

• dotancohen 28 minutes ago

Why the downvotes? I also was thinking that's a perfect candidate for swapping to disk.

• Sharlin 2 hours ago

Paging to disk has also become vastly more transparent, and less of a last resort, with M.2 SSDs. No more things slowing down 10x and endless HD noise when out of RAM.

• jmakov 4 minutes ago

Looking at the solution AMD bought, looks like Linux has a lot of room to improve regarding moving (compressed) inactive pages to disk: https://www.amd.com/en/products/software/mext.html

• Lio 8 hours ago

RAM compression sounds very useful but the thing I really need extra RAM for is local inference.

Since the models are effectively highly compressed data already my assumption is that RAM compression won't help improve that much (I'm assuming unified memory here as per the Framework Desktop). A bit like trying to compress a JPEG in a zip file.

Could anyone comment on that?

• throw-qqqqq 3 hours ago

The max theoretical ratio of (byte-independent) compression can be approximated using the Shannon entropy.

Most quantized GGUFs have a very high Shannon entropy, so are almost perfectly compressed already. A Q4_K_M quantization is often around +7.90 bits/byte and so is virtually incompressible.

Unquantized models (F16) are often around +7bits/byte for comparison.

https://en.wikipedia.org/wiki/Shannon%27s_source_coding_theo...

• vlovich123 3 hours ago

You are correct, compression doesn’t help reduce a model. That’s why quantization is inherently a lossy operation although there’s tricks to limit the perceived loss. That’s the only way to further compress the data.

One way to think about it is that if the weights were compressible, it’s a clear signal that better training could make the model smarter as there’s redundant information in the structure that could be used to store other meaning.

The other challenge with compressing weights of course is that you have to decompress them before you do math with them. Dequantizing weights is significantly cheaper and supports random access too (not that that matters too much but it helps in terms of leveraging SIMD techniques to do it in an embarrassingly parallel way)

• Powdering7082 2 hours ago

> redundant information in the structure that could be used to store other meaning.

Consider the induction heads, their W_O are generally expected to be the identity matrix and it is useful to have many of them at many layers (e.g. if you only had one induction head in the whole network you'd only be able to perform one induction circuit per token emitted)

That being said the attention heads are a small portion of the total network size

• matja 7 hours ago

> A bit like trying to compress a JPEG in a zip file

Interesting comparison, I wonder if there are loss-less compression schemes that are "weight-aware", about the statistical properties of model weights.

Back to that line - because (Huffman coded) JPEG images can be lossless recoded using arithmetic coding, which makes them smaller than if they were compressed with the best general-purpose compression algorithms/tools (e.g. `jpegtran -arithmetic < input.jpg > output.jpg` beats `xz -9 < input.jpg > output.jpg`). AC takes advantage of the properties of the image coding better than general-purpose compression tools on the output of the Huffman coding.

• rft 6 hours ago

The library I use for archiving compressed raw LLM weights ([1] , posted in my other comment) afaik at least reorders the weights to more easily compress them. They also have a paper linked, which I admittedly didn't read, that might have more background and tradeoffs. Likely they will have discussed methods to take advantage of the structure of weights.

[1] https://github.com/zipnn/zipnn#results

• rft 8 hours ago

I haven't tried it in RAM, but your reasoning matches what I saw when I looked at compressing weights for archiving them. The weights don't compress nicely with standard, especially fast, algorithms. Some more background in this repo [1] including example compression ratios. I would also worry about decompression speed, that gives you a hard bound on the throughput. If the numbers in this repo are accurate, you likely hit the throughput limit of decompression way before you hit the memory limit, even considering the space savings and thus higher effective throughput.

[1] https://github.com/zipnn/zipnn#results

• strobe 4 hours ago

it interesting because usually on workstation the browser & electron apps it's that holding much of the memory hostage (it's very common to see that browser consuming 20-30gb on 64gb system), so may be if it will be significant compression win on that side it leads to more memory for model but how much performance penalty would be for inference in that case?

• kalcode 8 hours ago

I don't know at all. But I've been playing with oMlx and Splash. Using Pi there are compression extensions like the billion-context. I suspect your right.

But all seem to have massive issue boards. What I did see was oMlx release clustering so you can string 3 macs and have 3 times the memory or use one for prefilling accelerating.

Which I thought was neat and what I'll likely poke at instead of getting more ran.

• 0123456789ABCDE 7 hours ago

perhaps i'm not pilled enough for this conversation, but aren't you conflating two disparate concepts — model-weights and context-window?

• kalcode 3 hours ago

Yah I think I am conflating it. I was thinking using the ram more effectively to begin to squeeze more, one of those is context size. Less VRAM the less context you can handle, so there always a lot of tuning to find that sweet spot.

So my mind on that.

• hedgehog 3 hours ago

As others have noted zswap is usually a better choice than zram, additionally depending on your situation it may be worth checking which algorithm it's using as there are a few choices (zstd, lz4, etc) and the defaults vary by distro. zstd is the right choice IMO unless you're in a situation where you know better.

• jakozaur 8 hours ago

> Memory compression is not new. If you have a Windows or Mac device you are already using it.

Yes, macOS has had it enabled by default since OS X Mavericks 10.9, released in October 2013. I’m surprised some desktop Linux distributions still require manual configuration to enable it.

For browser tabs, though, I think a better solution is automatic tab closing, using something like the Tab Wrangler extension for Chrome. Collecting tabs comes naturally; we’re much worse at closing them.

• xnx 4 hours ago

Chrome has had a built-in tab-sleeping Memory Saver feature for 4 years: https://blog.google/products-and-platforms/products/chrome/n...

• benjiro29 3 hours ago

"For browser tabs, though, I think a better solution is automatic tab closing" ... the better solution is to actually offload tabs. The issue with Chrome/Edge/... is not your tabs itself but the huge amount of memory loaded for GPU operations.

Do Shift+Esc and watch how large the GPU memory usage is. Often 2/3 to 50% of your actual tab usage.

Ironically, its not the closing of tabs that bothers me, but the fact that tab order changes, what slows my productivity/muscle memory down. And its the same reason for a lot of people why they keep tabs open.

I never understood why we do not have a basic snapshot / sleep that offloads a tabs memory on disk (and dumps the GPU memory), aka a ghost tab. And fast loads when you view the tab. Sure, there may be a small delay but it can save so much memory, while people can keep their tabs open/organized.

Some extensions try to mimic that but its often a crude solution because they do not have deeper access to the webview2 engine.

• jve 7 hours ago

Wait, Edge on windows automatically puts tabs to sleep when they are unused (https://explore.microsoft.com/en-us/edge/features/sleeping-t...). I think edge weren't even the first one, thus being kinda surprised I see chrome needs extension for that?

• evenfrost 7 hours ago

For Chrome I recommend The Marvellous Suspender, which can auto-suspend unused tabs. Has been a life-saver for me for quite a while.

• jamesgeck0 4 hours ago

I thought suspend plugins became redundant when Chrome started shipping a built-in auto-suspend. Is there still a reason to use them?

• kasabali 2 hours ago

They provide more granular options on when and what to suspend compared to crude heuristics of the built in feature.

• aa-jv 7 hours ago

>I’m surprised some desktop Linux distributions still require manual configuration to enable it.

Its a user choice and should be a user-facing knob because there are times it is inappropriate for use, such as in safety-critical circumstances, certain realtime realities, and so on. It should probably be on by default for desktop Linux, but off by default for every other application a distribution may be targeting ...

• flowerlad an hour ago

In the 1990s there was a third-party add-on for Windows called SoftRAM95 [1] that doubled your RAM using compression. That one turned out to be a scam though [2].

[1] https://en.wikipedia.org/wiki/SoftRAM

[2] https://devblogs.microsoft.com/oldnewthing/20211111-00/?p=10...

• cogman10 4 hours ago

Don't use Zram, use Zswap. Especially if you want to swap to disk.

https://chrisdown.name/2026/03/24/zswap-vs-zram-when-to-use-...

• mrob 3 hours ago

I never want to swap to disk. If I'm ever in that situation, it means I did something wrong, so I want my userspace OOM killer to trigger and inform me of my mistake immediately instead of wasting time and SSD endurance delaying the inevitable. But zram with lz4 compression is effectively free RAM in most circumstances, so there's little reason not to enable it.

• dsp_person 2 hours ago

Good point, dumping to SSD isn't ideal. I think I'm gonna start trying to set memory limits on programs with systemd-run so they can self-limit themselves.

• 01HNNWZ0MV43FF an hour ago

For today's 10,000, do `sudo apt-get install earlyoom` and thank me later

• teravor 2 hours ago

> Especially if you want to swap to disk.

if you don't want to swap to disk you should not use zswap.

zram is ideal in that scenario, though it may complicate OOM killer considerations (you may want a userspace one).

• ciupicri 4 hours ago

I've tried for running bsdiff and zswap was slower and spilled out data to the disk (which would wear an SSD).

• sammatilda 9 hours ago

I just discovered zram thanks to claude after installing fedora on a new computer and man I was blown away by both zram and fedora. Fedora amongst the linux distributions for some reasons has really got everything that an end user needs and the whole experience is just way smoother than anything I have used in 25 years on linux.

I am hoping to switch my dad from ubuntu to fedora in a month or so because he has 16 GB ram and this seems like something most people dont know.

• mkesper 3 hours ago

zram has inherent problems and is superseded by zswap. https://chrisdown.name/2026/03/24/zswap-vs-zram-when-to-use-...

• hofiflo 2 hours ago

I have a laptop with soldered RAM, a whole whopping 16GB of it. Without zswap or zram, it’s borderline unusable with web browsing, a bunch of terminals, mail client, etc. open. Maybe it’s a skill issue on my side, but only zram makes it work properly without hickups due to the OOM killer taking too long to kick in. Since switching from zswap to zram, I basically don’t encounter OOM situations and corresponding lockups anymore at all. Just my personal anecdote :)

• adgjlsfhk1 an hour ago

zswap+earlyoom/systemd-oomd is the optimal combo. Unfortunately, very few desktops ship this/configure it correctly.

• anthk 2 hours ago

Not in my case. Both a NUC with 8GB of RAM and a netbook with 1. Zram ran better. The least you touch the disk, the better.

• kasabali 2 hours ago

superseded when? both have inherent problems and their usecases and I got sick of this meme of pushing zswap as the superior solution.

• nico 9 hours ago

Wow, very cool. Is this like the old "RAM doubler" for Mac OS (or like Johnny Mnemonic's "Pemex MemDoubler")? :)

• Lio 8 hours ago

It's funny, I switch from Fedora back to Ubuntu last year.

I really like Fedora in that it seems very up to date package wise but I found it requires a reboot every time I update using the UI updater.

It's better using the dnf command but it still felt a bit lumpy compared to apt.

• nosrepa 3 minutes ago

You can turn that off in the settings for discover.

• mritzmann 8 hours ago

Install "needrestart", and you'll see that a reboot would be useful in Ubuntu, too. Many running programs still use the old version of a shared library even after it has been updated. With so many security updates these days, it almost always makes sense to reboot.

• amelius 7 hours ago

Could this be one of the tricks the M-series cpus are pulling behind the scenes to make them look faster?

• swiftcoder 3 hours ago

It's nothing to do with the CPUs. Apple implemented this OS-wide back in the 2010s, long before the M-series was on anyone's radar.

• jrmg 4 hours ago

It’s definitely one of the tricks the Neo is pulling behind the scenes to make 8Gb be ‘enough’.

• speed_spread 8 hours ago

I like Fedora too but I'm pretty sure Ubuntu also has zram. You just need to enable it.

• Juvination 4 hours ago

What a fun loop through time. I remember downloading programs to free up ram in the early 2000's, then as RAM became more ubiqutous and programs were still small you could run them directly on RAMDisk. (I did this with Path of Exile about 10 years ago to avoid lag.) Now we are working back to getting the most out of our ram.

• myrandomcomment 3 hours ago

MacOS does this by default for inactive pages. On my current system with 18GB of RAM I show 4.80GB for Apps, 3.16GB Wired and 5.06GB Compressed.

• Lerc 4 hours ago

I have to wonder if the better solution would be for browsers (and apps that are effectively broswers) to compress their data proactively.

I find that the ratio of browserish memory use to that of other programs is enough to render the latter insignificant most of the time.

• anthk 2 hours ago

Browsers can just suspend tabs. If they are separate processes, just send a SIGSTOP except for the actual active tab and run SIGCONT upon switching.

• nukanse 7 hours ago

For a programmer, on many cases, it pays to compress the data, to improve RAM IO, because the alu may already be doing nothing meanwhile waiting for the data from ram, so you can use that time to decompress, process, compress, and store the result. A lot of code today is bottlenecked by IO. You spend a lot of effort optimizing with SIMD, processing the data super fast, and then the speed it's wssted because there is not enough bandwidth to even send the result to ram. Modern cpu should include more hardware support for memory compression

• certyfreak 8 hours ago

I switched to Fedora some time ago and only recently learned about zram. I was hitting full system memory(16GB) during normal use, and after increasing my zram to 16GB, I was blown away. I had initially planned to buy additional ram.

• roosgit 10 hours ago

MacOS has been doing this for quite a while now. I was a bit surprised this wasn’t the default for most Linux distros, although I think Pop!_OS (what a name!) has had zram enabled for a few years already. I turned it on on one of my servers (1GB RAM) and it works fine.

• kachnuv_ocasek 9 hours ago

Fedora has had zram on by default for at least five years now.

• ChocolateGod 3 hours ago

zram relies on the swap subsystem, macOS memory compression does not rely on pages being swapped.

• anthk 2 hours ago

You can enforce the swappiness to 100 and virtually work in the same way.

• mrob 44 minutes ago

Maximum swappiness is 200. Setting it higher than 100 is possibly a good idea when using zram.

• aktenlage 7 hours ago

So, if it is used as swap, that means to use the data, it first needs to go to the CPU, then back to regular RAM, then back to the CPU.

Isn't that wasteful? The CPU's caches may help a bit, but I would guess first a huge block is going through the decompression, so only the last bits are still in the cache, when the actual usage starts.

• altcognito 3 hours ago

It's funny that MS didn't integrate memory compression until 2015. From ye olden days, we used "RAM doublers" in MSDOS, which were a bit of a different beast and took a performance hit due to simpler implementation, so some of us aren't "excited" by the cost of packing things in with compression. It is a bandaid for processes that lie somewhere between being needed and not (otherwise it would goto swap right?)

If it avoids hitting the disk I get it, but to some of us, that just means it's time to buy more RAM

• rustyhancock 8 hours ago

I've used zswap on most of my systems and generally find it beneficial especially as (de)compression can be very fast these days.

What's interesting to note is that I've occasionally wondered why isn't the swap partition compressed.

If you have it on an NVMe drive it probably is as is all data! The controller usually transparently does it as it writes to/from NAND.

So the kernel sees uncompressed fixed block pages and the speed boosts happen with data arriving faster when read or written to flash.

• mkesper 3 hours ago

Where did you get that info? Sounds suspicious.

• deltoidmaximus an hour ago

I didn't think controllers generally did any compression but I remember once that on old sandforce controllers if you did something like write all zeros it wouldn't actually overwrite anything instead just mapping to another block of zeros. Which sounded more like on device dedupping than compression.

• close04 4 hours ago

> I've used zswap on most of my systems and generally find it beneficial

I started using zswap recently but didn't have the time yet to measure the benefit. Does it benefit machines with low amounts of RAM and wimpy CPU (like a RPi3)?

> The controller usually transparently does it as it writes to/from NAND.

In the consumer SSD space the last controllers I know did on-the-fly compression were SandForce [1], probably 15 years ago, when minimizing writes and saving the little capacity available was imperative. I don't think any other desktop SSDs do this now. A bit more common in enterprise models like ScaleFlux CSD.

[1] https://en.wikipedia.org/wiki/SandForce#Products

• grandlimelabs 2 hours ago

Make sure to stress-test compression and decompression for whatever you're doing before you go jumping into relying on it, though.

• pyaamb 3 hours ago

I wonder what the theoretical limits are of semantic compression for LLM input/output (eg. "Can you please send me the final report by Friday?" -> "Send final report by Friday." -> sr(FINAL, DEADLINE=FRIDAY)) that can still be recovered back to English

• NegativeLatency 3 hours ago

https://github.com/microsoft/LLMLingua one such library I’m aware of

Tried porting it to swift, was hoping it would make mobile local models more useful for a project I was working on but it was hurting the accuracy too much. Can be very task dependent on how much you can compress. https://github.com/nburns/llmlingua-swift

My specific use case was using a LLM on segments of labeled data from a different faster model as a final pass.

• 1970-01-01 2 hours ago

This feels like the kind of thing that leads to 0day. Compression can defeat security. Delta frames. Compression bombs.

https://www.youtube.com/watch?v=4icQwducz68

https://www.youtube.com/watch?v=IXkX2ojrKZQ

• IronWolve 3 hours ago

I remember the compression rage back on my amiga, had both ram and file compression, since you had to get as much room as you could with limited ram and a floppy.

• bismanawaz 2 hours ago

I was wondering if its the agents itself or the browsers that they open fill up the RAM?

• 72deluxe 6 hours ago

Having viewed that page, I cannot fathom how Firefox is using 27GB of RAM in his screenshot?!

• alpaca128 3 hours ago

I've seen a single YouTube browser process use 8GB on my desktop, so I'm not that surprised. YT eats up whatever is available if you leave some tabs open for long enough, fortunately about:processes exists.

• Sopel 3 hours ago

from my experience it would require roughly 100 active youtube tabs

• Ecno92 10 hours ago

Since I am using Claude with parallel sessions in different workspaces I started to run out of RAM.

Instead of buying more RAM, which meant that I should replace my device, I decided to implement zram. This compresses memory. Now I can do more with the same hardware.

In many cloud environments compression is not enabled. I am curious to see if the same gains can be made in such environment.

• XYen0n 9 hours ago

You can enable it yourself, for example using https://github.com/systemd/zram-generator.

• Ecno92 7 hours ago

I did! I am actually the author of the post! ;-)

• aa-jv 7 hours ago

Great article, thanks for sharing the details .. only thing I'd add is that you should put a bit of emphasis on the fact that this is not a one-size fits-all setting - users should very much apply it when appropriate to their latency budgets...

• ChrisRR 8 hours ago

> Compressing memory does not come with downsides. It takes a little bit more from your CPU and adds latency to some processes

It sounds like those are downsides

• Ecno92 7 hours ago

I believe I have written this not in the best way. (I have uploaded a slightly improved version)

I did not really notice a large performance impact.

Unless you are in an environment where compute performance is critical, I think this is something interesting to try.

• Rohansi 8 hours ago

It's basically in-memory swap. If you have swap then you already have the added latency (but worse) and I/O usage instead of CPU. Like swap, the downsides only come into play under high memory pressure.

• aa-jv 7 hours ago

They are downsides in cases where an application has to escalate a critical fault as quickly as possible - indeed where every nanosecond counts - and a process waiting for page restoration is going to be delayed even an intolerable amount.

It should be a user switch and probably will become one in most Linux desktop distributations, I would wager. However, I would not enable it - I run Ubuntu Studio for every last little bit of latency it gives me in a realtime audio-capture application, and on those systems were it to become default-on by way of distro update, I'd be kinda miffed.

• xxs 8 hours ago

That's a terrible statement. Perhaps it can apply to certain setups where compression (and decompression) shows decent results, in lots of applications it'd be a massive downgrade.

• Rohansi 8 hours ago

zram does not compress all of your RAM. It only compresses inactive blocks of memory that would be eligible for swap, if you had swap enabled.

• aa-jv 7 hours ago

The distinction is in the distribution - is the Linux bootable for an end user or is it for a rack-mount industrial application - since anyway the kernel configuration has to be involved to have zswap effectively applied at kernel runtime.

• Stitch4223 7 hours ago

They are not selling it well.

It’s like saying that in order to breathe you have to use your nose or mouth. Which is bad if you want to retain the oxygen that is inside your lungs.

There are always scenario’s where memory compression is an outright bad idea. Just like trying to breathe under water.

• MadameMinty 8 hours ago

"does not come without downsides" + "does come with downsides" race condition

• distantsounds 4 hours ago

Hilarious ending to the article. You expect some implementation details with a Getting Started section, instead you get a "check the arch wiki" link.

• nchmy 2 hours ago

Yeah that was disappointing

• kiicia 8 hours ago

nice try Ram Altman

• yummybear 8 hours ago

"Compressing memory does not come with downsides. It takes a little bit more from your CPU and adds latency to some processes"

Which one is it?

• tooheavy 4 hours ago

Compression is fine as long as the CPU doesn't become the bottleneck.

• baud9600 7 hours ago

You’d hope with these amazing GPUs today, that some cycles can be used to compress RAM very efficiently. So many parallel cores, surely we can get even better compression from this latent hardware?

• BenjiWiebe 3 hours ago

I'm under the impression that GPU latency is the problem here for on-the-fly de/compression.

There might be gains by having the GPU recompress with a higher compression level in the background though.

• 1023bytes 3 hours ago

Do not buy RAM, download more RAM

• fernandogrd 4 hours ago

Things I did: - Zswap instead of zram. - Unload browser tabs (my own private extension. - Force idle cli AI agents to go to disk swap earlier.

• LoganDark 7 hours ago

Windows doesn't do memory compression if the page file is not enabled. I never particularly saw the point of the page file because I don't enjoy swapping, but it appears that the memory management system disproportionately depends on it to the point where it simply refuses to work properly with it off. So make sure that's turned on if you want memory compression. (Do not let it auto-size or it will happily fill up your whole drive, set it to something reasonable)

• vardump an hour ago

Windows needs to have a backing store for every page allocated.

So shouldn’t disable pagefile, unless it’s a disk space issue. Windows probably won’t use it much anyways if you have enough RAM.

• fred_is_fred 4 hours ago
• esafak 2 hours ago

This used to be a whole product category. For hard drives too!

DiskDoubler, Stacker, SuperStor, DoubleDisk...

• pshirshov 4 hours ago

Vectors do not compress.

• UltraSane 2 hours ago

IBM Power systems have hardware RAM compression.

• cubefox 7 hours ago

So why is zswap (basically zram+swap) not enabled by default everywhere?

• aa-jv 7 hours ago

Because it is a user choice, and there are applications where it is inappropriate. For desktop Linux it should probably be on, as long as its clear to the user - but yeah, for many other Linux use cases its inappropriate.

• jrmg 4 hours ago

“Because it is a user choice”

That’s true of everything. Default setups make those choices.

• cubefox 6 hours ago

Maybe it should generally be on and and only switched off when it is inappropriate.

• cestith 4 hours ago

Maybe it should be generally on for desktop-focused distros and generally off for server-focused ones. The distros that focus on doing both well might want to recommend it in the installer when told it's primarily a desktop installation and explain the tradeoffs.

For a server, it really depends on what kind of service you're providing whether it would be helpful. We might want to let server admins, SREs, production engineers, or platform engineers to make an active decision about it.

• cubefox 3 hours ago

I have a hard time imagining cases where swapping or running out of RAM is preferable to RAM compression.

• cestith 2 hours ago

In most cases you'll really want zswap rather than zram anyway.

There are plenty of scenarios in which servers are run with only nominal swap sizes or none at all and systems don't run out of RAM.

Let me size my hypervisor cluster to demand and let the system decide where to place the guests. If the hypervisors are crashing due to full RAM, that's down to planning or budget issues and not a reason to put additional unpredictable latency underneath the guests.

Let me size my SDI to UDP TS video streaming servers to the number and size of streams they'll service. There's not much in their memory pages that's going to ever be idle enough to compress, so why boot the kernel configured to do that? It's just risking extra packet IAT for buying not much benefit.

But in general, yes, zswap would be a good thing compared to swapping to a drive, unless you are mostly swapping things that are really truly idle a long time. Default swappiness on a lot of distros is around 60 by the way, and on servers it's often set closer to 10 or 15.

• ChocolateGod 3 hours ago

zswap works very differently to zram.

• varispeed 2 hours ago

Do not eat, drink water.

As usual, working class is being told to tighten the belts whilst the rich get insanely richer.

Fuck that.

• ifloop 27 minutes ago

just download more RAM

• dist-epoch 8 hours ago

> If you have a Windows or Mac device you are already using it

Technically yes, practically on Windows memory compression is not used.

I have Windows 11, 128 GB RAM, and my memory stats show: 42 GB in use, 380 MB compressed.

• sheo 8 hours ago

You have plenty of RAM free. Compressing at that point is increasing latency for no good reason. Unused RAM is wasted RAM

I'm a Linux user myself, but I think it would start compressing it when there would be less than 25% free

• jauntywundrkind 8 hours ago

In many systems, adding compression makes not just storage better but increases the io you get from a system too. Here's Valkey 9.2 compression figures showing that: https://www.phoronix.com/news/Valkey-9.2

That's for RDB persistence. https://valkey.io/topics/persistence/

I wonder if there's any similar wins with ram? That some workloads would see net wins from compression. Some cost of cpu, but increasing net throughput significantly.

• hinkley 7 hours ago

Okay, Johnny Mnemonic.

• DeathArrow 8 hours ago

I have built my PC with core i7 14700K, RTX 3090,128 GB DDR3, 2TB SSD, 8TB HDD about 3 years ago.

Still perfectly usable and I won't upgrade until prices come down. Even used prices are terrible now.

• globular-toast 8 hours ago

Mine is an i7 4790K with 32GB of RAM and it's more than usable, I find it quite nippy.

The main thing I regret is not maxing out the memory on my server. At first 32Gi seemed more than I'd ever need, but now it's feeling quite anaemic.

• theandrewbailey 8 hours ago

> 128 GB DDR3

Typo DDR5?

• DeathArrow 7 hours ago

Yes, it was a typo, I use DDR4.

• xxs 8 hours ago

of course, it supports only that type of memory. 128GB on a desktop 2 ram channel machine is massive, too

• theandrewbailey 8 hours ago
• mzhaase 9 hours ago

Zram vs Zswap: https://chrisdown.name/2026/03/24/zswap-vs-zram-when-to-use-...

> If in doubt, prefer to use zswap. Only use zram if you have a highly specific reason to.

> In terms of architecture:

> zswap sits in front of your disk swap, compresses pages in RAM, and automatically tiers cold data to disk. It integrates directly with the kernel's memory management and distributes pressure gracefully.

> zram is a compressed RAM block device with a hard capacity limit. When you put swap on it and it fills up, there is no automatic eviction, and the kernel has very little leverage to do anything about the situation. The system either OOMs or falls back to lower-priority swap, causing LRU inversion (see below). It only really makes sense for extremely memory-constrained embedded systems, diskless setups, or cases with specific security requirements around keeping private data off persistent storage. Swap on zram is also increasingly unsupported upstream.

• keybored 7 hours ago

I enjoyed that Zram article a lot way back when.

( https://news.ycombinator.com/item?id=47500746 )

It’s long and more satisfying than this In These AI Times wrapper.

• speed_spread 8 hours ago

What if I loathe swap? The I/O hit of hitting swap, even with SSD, always mean a severely degraded desktop experience. I often end up closing applications to free up RAM or would just order more RAM back when it didn't involve taking a third mortgage.

I would rather have the system tell me there's not enough memory than try to pretend there's an infinite amount of it and then slow to a crawl without apparent reason. Unix memory allocation is daft. Desktop swap to block never worked, never will.

• adgjlsfhk1 44 minutes ago

You still want swap, The part you're missing is a good oom strategy. Your system slowing a ton has to do with needing to access swapped memory. Swap is still very useful when you have background tasks that aren't running, but are still using a bunch of RAM. The trick is that if you suddenly start reading a lot of that data repeatedly while being in that sate, you need to oom something quickly.

• mrob 2 hours ago

Agreed. IMO, zswap is the one that requires a "highly specific reason", while zram (with lz4) should be enabled by default.

• izacus 4 hours ago

You seem to be fundamentally misunderstanding what zswap is and are instead griping about something unrelated.

• messe 9 hours ago