<p>Looks like a couple of interesting <a href="https://types.pl/tags/NixOS" class="mention hashtag" rel="tag">#<span>NixOS</span></a> forum threads dead-ended earlier than I would have liked.</p><p>I think there would be value in having zram replace tmpfs for /tmp on a lot of systems. It takes a perf penalty to compress with lz4, etc. but you can save a lot of space. But what is the use case folks are asking… well /tmp in RAM it seems would often be ideal if you are say *compiling a bunch of <a href="https://types.pl/tags/Nix" class="mention hashtag" rel="tag">#<span>Nix</span></a> derivations*, do that in memory can save on the NVMe wear as well as the high, high temps these devices run. Some things build quite large like the Linux kernel that needs something over 16GB of tmpfs space (I don’t know yet, still rebuilding @ 20 GB) & a lot of folks, especially on laptops don’t have a spare 16 GB of RAM to work with… which is where zram can come in to save space there.</p><p>If I was more knowledgeable about disks/hardware/systemd, I would love to take a (f)stab at it. I have a very finicky drive that does not respond well to the heavy IO thrashing of certain compiles (where it *seems* to overheat then drop off the bus), but so far with tmpfs + zram is not exhibiting the same issues. I’m lucky to have 64 GB in a laptop to try this out, but my old backup (that I’m typing on) only has 16 GB as do many folks’ devices.</p>
