<?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>Mlsys on Tyler Zhu</title>
    <link>https://tylerzhu.com/blog/tags/mlsys/</link>
    <description>Recent content in Mlsys on Tyler Zhu</description>
    <generator>Hugo -- 0.154.3</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 02 Feb 2026 00:00:00 -0800</lastBuildDate>
    <atom:link href="https://tylerzhu.com/blog/tags/mlsys/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>FSDP for Dummies</title>
      <link>https://tylerzhu.com/blog/2026/02/fsdp-for-dummies/</link>
      <pubDate>Mon, 02 Feb 2026 00:00:00 -0800</pubDate>
      <guid>https://tylerzhu.com/blog/2026/02/fsdp-for-dummies/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve always struggled to understand the intuitions behind Fully Sharded Data Parallel beyond the high level idea of &amp;ldquo;shard everything.&amp;rdquo; Without a systems background, the fundamental primitives like &amp;ldquo;all-reduce&amp;rdquo; and &amp;ldquo;reduce-scatter&amp;rdquo; aren&amp;rsquo;t in my vocabulary. But FSDP conceptually is not complicated, especially once you state what the goals are (the rest is nearly necessitated by the engineering).&lt;/p&gt;
&lt;p&gt;This post is an attempt to deconstruct the algorithm from first principles as a non-systems person. I will bring up the primitives in their specified context, which I think helps reinforces the intuition much better. Most ML researchers have a stronger understanding of the models, params, and optimizer processes than the systems jargon anyways.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
