<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Memory on Tony Metzidis</title>
    <link>https://tonym.us/tag/memory.html</link>
    <description>Recent content in Memory on Tony Metzidis</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 02 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://tonym.us/tag/memory/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taming GCE Memory Tax: Disabling OS Login and OS Config on Small Instances</title>
      <link>https://tonym.us/taming-gce-memory-tax-oslogin-osconfig.html</link>
      <pubDate>Fri, 02 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://tonym.us/taming-gce-memory-tax-oslogin-osconfig.html</guid>
      <description>&lt;p&gt;Google Compute Engine&amp;rsquo;s &lt;code&gt;e2-micro&lt;/code&gt; instances are a staple of the GCP Free Tier, offering 2 vCPUs and roughly 1 GB of RAM (969 MiB usable). They are ideal for lightweight bastions, cron runners, and small test beds. However, if you run memory-sensitive workloads—such as Go builds, package extractions, or continuous process forks—you may have experienced intermittent, baffling SSH connection timeouts and unresponsive terminals.&lt;/p&gt;&#xA;&lt;p&gt;The root cause is rarely your application alone. By default, GCE provisions a suite of Google guest daemons that consume a disproportionate share of resident memory on small VMs, creating an environment primed for SSH exhaustion.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
