<?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>Paper Reading on Duo&#39;s Tech Blog</title>
    <link>https://duoan.github.io/tags/paper-reading/</link>
    <description>Recent content in Paper Reading 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>Mon, 13 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://duoan.github.io/tags/paper-reading/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Paper Reading: ARGUS — Always-On Tracing at 10,000&#43; GPU Scale</title>
      <link>https://duoan.github.io/posts/argus-tracing-at-10000-gpu-scale/</link>
      <pubDate>Mon, 13 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://duoan.github.io/posts/argus-tracing-at-10000-gpu-scale/</guid>
      <description>&lt;h1 id=&#34;paper-reading-argus--always-on-tracing-at-10000-gpu-scale&#34;&gt;Paper Reading: ARGUS — Always-On Tracing at 10,000+ GPU Scale&lt;/h1&gt;
&lt;p&gt;What Tencent built to catch fail-slow training jobs on 10k+ GPU clusters with under 2% overhead — plus Modal remasurements of always-on &lt;code&gt;torch.profiler&lt;/code&gt; / &lt;code&gt;nsys&lt;/code&gt; overhead and a tiny demo of the KDE + W₁ detection math.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Paper:&lt;/strong&gt; &lt;a href=&#34;https://arxiv.org/abs/2606.20374&#34;&gt;ARGUS: Production-Scale Tracing and Performance Diagnosis for over 10,000-GPU Clusters&lt;/a&gt; (Zhou et al., Tencent, arXiv 2606.20374, submitted to ATC 2026)&lt;/p&gt;
&lt;h2 id=&#34;tldr&#34;&gt;TL;DR&lt;/h2&gt;
&lt;p&gt;Large LLM training jobs are synchronous: one slow rank, link, or host-side stall can waste thousands of GPU-hours without triggering a hard failure. Existing tools split into two camps:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
