<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Distributed Training on Nalar</title>
    <link>https://nalar.dev/tags/distributed-training/</link>
    <description>Recent content in Distributed Training on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 06 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/distributed-training/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Reduce Transformer Activation Memory with Sequence Parallelism</title>
      <link>https://nalar.dev/reduce-transformer-activation-memory-with-sequence-parallelism/</link>
      <pubDate>Sun, 06 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/reduce-transformer-activation-memory-with-sequence-parallelism/</guid>
      <description>&lt;p&gt;Large transformer training can run out of accelerator memory even after the model&amp;rsquo;s weights are split across several devices. The reason is easy to miss: tensor parallelism can shard expensive matrix multiplications while some intermediate activations remain replicated on every worker in the tensor-parallel group.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Sequence parallelism&lt;/strong&gt; removes part of that replication. For operations that work independently on each token, it partitions activations along the sequence dimension so each tensor-parallel worker keeps only a slice of the tokens. The workers temporarily reconstruct or reduce data where the tensor-parallel computation requires communication, then return to sequence-sharded activations.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
