<?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>Pipeline Parallelism on Duo&#39;s Tech Blog</title>
    <link>https://duoan.github.io/tags/pipeline-parallelism/</link>
    <description>Recent content in Pipeline Parallelism on Duo&#39;s Tech Blog</description>
    <image>
      <title>Duo&#39;s Tech Blog</title>
      <url>https://duoan.github.io/images/papermod-cover.png</url>
      <link>https://duoan.github.io/images/papermod-cover.png</link>
    </image>
    <generator>Hugo -- 0.153.1</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 16 Mar 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://duoan.github.io/tags/pipeline-parallelism/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pipeline Parallelism from First Principles: Why GPipe Split the Batch</title>
      <link>https://duoan.github.io/posts/pipeline-parallelism-gpipe/</link>
      <pubDate>Sun, 16 Mar 2025 00:00:00 +0000</pubDate>
      <guid>https://duoan.github.io/posts/pipeline-parallelism-gpipe/</guid>
      <description>&lt;h1 id=&#34;pipeline-parallelism-from-first-principles-why-gpipe-split-the-batch&#34;&gt;Pipeline Parallelism from First Principles: Why GPipe Split the Batch&lt;/h1&gt;
&lt;p&gt;Pipeline parallelism starts with a useful accident: a Transformer is already a chain. If one GPU cannot hold the whole stack, put consecutive blocks on consecutive GPUs and send activations across stage boundaries.&lt;/p&gt;
&lt;p&gt;That solves capacity. It does not solve throughput. A naive layer split turns an expensive cluster into a queue where most devices wait. GPipe&amp;rsquo;s contribution was to make the queue busy by slicing the mini-batch into micro-batches and recomputing activations instead of storing everything (&lt;a href=&#34;https://arxiv.org/abs/1811.06965&#34;&gt;arXiv:1811.06965&lt;/a&gt;).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
