<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Benchmarks on Tony Metzidis</title>
    <link>https://tonym.us/tag/benchmarks.html</link>
    <description>Recent content in Benchmarks on Tony Metzidis</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 07 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://tonym.us/tag/benchmarks/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>WSL2 vs WSL3 Benchmarks: Performance, Memory, and Syscall Scaling</title>
      <link>https://tonym.us/wsl2-vs-wsl3-benchmarks.html</link>
      <pubDate>Wed, 07 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://tonym.us/wsl2-vs-wsl3-benchmarks.html</guid>
      <description>&lt;p&gt;With the release of the WSL 3.x stack, Microsoft bumped the default virtualization runtime and advanced the shipped guest kernel from the 6.6 LTS branch up to 6.18.&lt;/p&gt;&#xA;&lt;p&gt;WSL upgrades often claim generalized performance gains, but marketing bullet points rarely translate directly to developer workloads. To see what actually changed under the hood, I ran side-by-side benchmark suites comparing &lt;strong&gt;WSL 2.6.3.0&lt;/strong&gt; (Linux kernel &lt;code&gt;6.6.87.2&lt;/code&gt;) against &lt;strong&gt;WSL 3.0.2.0&lt;/strong&gt; (Linux kernel &lt;code&gt;6.18.40.1&lt;/code&gt;).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
