<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Gzip on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/gzip/</link>
    <description>Recent content in Gzip on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 01 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/gzip/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux Compression Tools: zstd vs brotli vs lz4 vs gzip for Servers Guide 2026</title>
      <link>https://www.pistack.xyz/posts/2026-06-01-linux-compression-tools-zstd-brotli-lz4-gzip/</link>
      <pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-01-linux-compression-tools-zstd-brotli-lz4-gzip/</guid>
      <description>&lt;p&gt;Compression is everywhere in a self-hosted stack — web server responses, log rotation, database backups, container image layers, and archive transfers. Choosing the right compression algorithm can dramatically reduce storage costs, speed up transfers, and lower bandwidth usage. But with zstd, brotli, lz4, and gzip all available, which one should you deploy where?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
