<?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>Memory on Rishi Daftary</title>
    <link>/tags/memory/</link>
    <description>Recent content in Memory on Rishi Daftary</description>
    <image>
      <title>Rishi Daftary</title>
      <url>/images/papermod-cover.png</url>
      <link>/images/papermod-cover.png</link>
    </image>
    <generator>Hugo -- 0.163.3</generator>
    <language>en</language>
    <copyright>Rishi Daftary 2025</copyright>
    <lastBuildDate>Sat, 25 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/memory/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Go 1.26 vs .NET 10 — A Deep Dive into Memory Allocation</title>
      <link>/posts/dotnet10-vs-go-memory-comparison/</link>
      <pubDate>Sat, 25 Jul 2026 00:00:00 +0000</pubDate>
      <guid>/posts/dotnet10-vs-go-memory-comparison/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Most language comparisons focus on execution speed, but memory allocation is often the more practical concern:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Higher allocation&lt;/strong&gt; → more GC pressure → unpredictable latency spikes&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Lower allocation&lt;/strong&gt; → better cache utilization → cheaper hosting&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Allocation patterns&lt;/strong&gt; → determine infrastructure requirements and scalability limits&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This post compares &lt;strong&gt;total bytes allocated&lt;/strong&gt; by Go 1.26.5 and .NET 10.0 SDK (10.0.302) running identical workloads on the same hardware. Both are the latest stable releases as of July 2026.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
