<?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>Slurm on Route179</title>
    <link>https://route179.dev/tags/slurm/</link>
    <description>Recent content in Slurm on Route179</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>2026 Sheng Chen</copyright>
    <lastBuildDate>Mon, 03 Aug 2026 10:00:00 +1000</lastBuildDate>
    <atom:link href="https://route179.dev/tags/slurm/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building a Slurm GPU Cluster on AWS — and Fine-Tuning Qwen3-4B Across It</title>
      <link>https://route179.dev/2026/08/03/slurm-qwen-finetune/</link>
      <pubDate>Mon, 03 Aug 2026 10:00:00 +1000</pubDate>
      <guid>https://route179.dev/2026/08/03/slurm-qwen-finetune/</guid>
      <description>&lt;p&gt;Slurm is the workload manager that runs most of the world&amp;rsquo;s HPC and large-scale ML
training. This post walks through building a small Slurm GPU cluster on AWS from scratch,
and runs a distributed LoRA fine-tune of Qwen3-4B across two GPU nodes (8 GPUs total).&lt;/p&gt;
&lt;h2 id=&#34;why-slurm-for-training&#34;&gt;Why Slurm for training&lt;/h2&gt;
&lt;p&gt;If you already run Kubernetes, it&amp;rsquo;s worth being clear about why you&amp;rsquo;d reach for
Slurm at all. Kubernetes is a &lt;em&gt;service&lt;/em&gt; orchestrator — built to keep long-running
things alive and healthy. A training run is the opposite shape: a finite job that
grabs N GPUs, runs to completion, and exits. That&amp;rsquo;s a &lt;strong&gt;batch&lt;/strong&gt; workload, and Slurm
is a batch scheduler built exactly for it — with a real queue, &lt;strong&gt;gang scheduling&lt;/strong&gt;
(all your nodes start together or the job waits), and one-line multi-node launch via
&lt;code&gt;srun&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
