<?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>Dotnet11 on Rishi Daftary</title>
    <link>/tags/dotnet11/</link>
    <description>Recent content in Dotnet11 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.143.1</generator>
    <language>en</language>
    <copyright>Rishi Daftary 2025</copyright>
    <lastBuildDate>Sun, 15 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/dotnet11/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>.NET 11 vs Go 1.27: Runtime Async, 14 Workloads, and an ASP.NET Core Shootout</title>
      <link>/posts/dotnet11-vs-go127-benchmark/</link>
      <pubDate>Sun, 15 Nov 2026 00:00:00 +0000</pubDate>
      <guid>/posts/dotnet11-vs-go127-benchmark/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Last time I compared &lt;a href=&#34;https://rishidaftary.com/posts/dotnet10-vs-go-memory-comparison/&#34;&gt;Go 1.26 and .NET 10 strictly on memory allocation&lt;/a&gt;, and the conclusion was that the winner depended entirely on the workload: Go for strings and concurrency, .NET for collections and hash sets.&lt;/p&gt;
&lt;p&gt;This is the follow-up, with three changes that make it a much more interesting fight:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;.NET 11&lt;/strong&gt; (SDK 11.0.100, runtime 11.0.0) — including its new &lt;strong&gt;Runtime Async&lt;/strong&gt; implementation, which I explicitly enabled.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Go 1.27.4&lt;/strong&gt; — the latest release, built with &lt;code&gt;GOAMD64=v3&lt;/code&gt; to match .NET&amp;rsquo;s x86-64-v3 ReadyToRun baseline.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A wider benchmark surface&lt;/strong&gt; — 14 workloads instead of 6, plus an actual &lt;strong&gt;ASP.NET Core vs &lt;code&gt;net/http&lt;/code&gt;&lt;/strong&gt; requests-per-second comparison.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Both sides are Release builds on the same machine, and every number below comes from the same harness, the same data structures and the same algorithms.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
