<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Zram on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/zram/</link>
    <description>Recent content in Zram on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 29 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/zram/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux Compressed Swap Management: zram-generator vs systemd-swap vs zramd</title>
      <link>https://www.pistack.xyz/posts/2026-05-29-self-hosted-linux-compressed-swap-management-zram-generator-systemd-swap-zramd-guide/</link>
      <pubDate>Fri, 29 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-29-self-hosted-linux-compressed-swap-management-zram-generator-systemd-swap-zramd-guide/</guid>
      <description>&lt;p&gt;Memory pressure is one of the most common causes of server instability. When a Linux server runs out of RAM, the kernel invokes the OOM (Out of Memory) killer, terminating processes to free memory. Before reaching that point, the kernel uses swap space — either a swap partition/file on disk, or compressed RAM via zram. This guide compares three tools for managing compressed swap on Linux: &lt;strong&gt;zram-generator&lt;/strong&gt; (systemd-native), &lt;strong&gt;systemd-swap&lt;/strong&gt; (hybrid swap manager), and &lt;strong&gt;zramd&lt;/strong&gt; (simplified zram automation).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
