<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Gigabytes on Tenu Tech Brief</title>
    <link>https://cluster-site.onrender.com/tags/gigabytes/</link>
    <description>Recent content in Gigabytes on Tenu Tech Brief</description>
    <generator>Hugo -- 0.146.0</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 24 Feb 2026 06:02:58 +0000</lastBuildDate>
    <atom:link href="https://cluster-site.onrender.com/tags/gigabytes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How Go 1.24&#39;s Swiss Tables saved us hundreds of gigabytes</title>
      <link>https://cluster-site.onrender.com/posts/how-go-1.24s-swiss-tables-saved-us-hundreds-of-gigabytes/</link>
      <pubDate>Thu, 17 Jul 2025 00:00:00 +0000</pubDate>
      <guid>https://cluster-site.onrender.com/posts/how-go-1.24s-swiss-tables-saved-us-hundreds-of-gigabytes/</guid>
      <description>• Nayef Ghattas In Part 1: How we tracked down a Go 1.24 memory regression across hundreds of pods, we shared how upgrading to Go 1.24 introduced a subtle runtime regression that i</description>
    </item>
  </channel>
</rss>
