<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Sumit Sodhi</title>
    <description>The latest articles on DEV Community by Sumit Sodhi (@sumit_sodhi).</description>
    <link>https://dev.to/sumit_sodhi</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4224539%2F80a846a0-3738-4f9d-80e1-35d7c3a308d0.jpg</url>
      <title>DEV Community: Sumit Sodhi</title>
      <link>https://dev.to/sumit_sodhi</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sumit_sodhi"/>
    <language>en</language>
    <item>
      <title>A 125B model at 50+ tok/s on a 12 GB gaming card: what I changed in Strata</title>
      <dc:creator>Sumit Sodhi</dc:creator>
      <pubDate>Tue, 03 Nov 2026 15:13:42 +0000</pubDate>
      <link>https://dev.to/sumit_sodhi/a-125b-model-at-50-toks-on-a-12-gb-gaming-card-what-i-changed-in-strata-2cig</link>
      <guid>https://dev.to/sumit_sodhi/a-125b-model-at-50-toks-on-a-12-gb-gaming-card-what-i-changed-in-strata-2cig</guid>
      <description>&lt;p&gt;I run Qwen3.8-Flash-Next, a 125-billion-parameter mixture-of-experts model, on one RTX 3060 with 12 GB of video memory and 30 GB of RAM. Nothing leaves my PC. This post is about the fork I made to get there, what I measured, and what I have not tested.&lt;/p&gt;

&lt;h2&gt;
  
  
  Starting point: Strata
&lt;/h2&gt;

&lt;p&gt;The model is about 78 GB of files at the quantization I use (IQ3_S). It does not fit on a 12 GB card. &lt;a href="https://github.com/Niko1221/Strata" rel="noopener noreferrer"&gt;Strata&lt;/a&gt; by Niko1221 and contributors (MIT) solves that by keeping the most-used experts on the graphics card, putting more in RAM, and streaming the rest from the SSD. My fork, &lt;a href="https://github.com/sangharshadhyeta/Strata-HotRod" rel="noopener noreferrer"&gt;Strata-HotRod&lt;/a&gt;, makes that path faster and checks that answers stay correct.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I measured
&lt;/h2&gt;

&lt;p&gt;All of this is on one machine: RTX 3060 12 GB, Intel i5-12400F, 30 GB RAM, a 500 GB NVMe on a PCIe 3.0 link, Rocky Linux 9.6.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Answer (131K context)&lt;/th&gt;
&lt;th&gt;tokens/s&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Code, 500-650 tokens&lt;/td&gt;
&lt;td&gt;52-55&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Reasoning, about 1,000 tokens&lt;/td&gt;
&lt;td&gt;66-71&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Prose, 100-150 tokens&lt;/td&gt;
&lt;td&gt;50-53&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Long prompts, 262K context: an 8,554-token prompt is read in 16.9 s and answered at 52-54 tokens/s. A 45,398-token prompt takes 67-68 s to read, then the answer comes at 38-41 tokens/s. The next turn of that same conversation starts in 0.4-0.5 s, because the saved state is reused. The first message of a chat is the slow part: it waits on the SSD for the model's experts.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I changed
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;A learned look-ahead.&lt;/strong&gt; The engine guesses which experts the next layers will need and loads them early. Against the plain router, the guesses are right 85-88% of the time one layer ahead (router: 77-79%), 76-79% two layers ahead (66-69%), and 66-71% four layers ahead (55-58%).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Three tiers: card, RAM, SSD.&lt;/strong&gt; The hottest experts sit on the card, the next ones in a RAM tier sized from free memory, the rest on the SSD. Budgets and reserves are measured on your PC and kept across restarts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Expert placement from routing traces,&lt;/strong&gt; instead of a fixed guess.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Stand-in experts with a re-check.&lt;/strong&gt; To stay fast, some of a token's experts are replaced with similar ones already on the card.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pinned RAM segments&lt;/strong&gt; (on by default): about 9% faster on this PC.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Every change and its measurement is in the repo's docs, including ideas that did not help. For example, a learned read-ahead of lower-ranked guesses made decoding 23% slower on this PC, because the drive was already at its limit, so it stays opt-in.&lt;/p&gt;

&lt;h2&gt;
  
  
  Is the answer quality still good?
&lt;/h2&gt;

&lt;p&gt;In a small test (50 maths questions, 30 coding questions, answers read by hand), the stand-ins gave 47/50 and 30/30 correct, against 48/50 and 30/30 with nothing replaced. A test this small cannot show a difference of one or two answers either way. On MMLU-Pro (15 questions from each of its 14 subjects, 210 in all, thinking on, temperature 0) it scored 87.1%, 183 of 210. That is a small sample, so read it as a sanity check, not a leaderboard result.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I have not tested
&lt;/h2&gt;

&lt;p&gt;One card, one model, one PC, Linux only. Other GPUs, AMD, Windows, macOS and other model sizes may work in upstream Strata, but I have not run them, so I will not claim them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it, and tell me what you get
&lt;/h2&gt;

&lt;p&gt;The repo has the install steps and the full change log: &lt;a href="https://github.com/sangharshadhyeta/Strata-HotRod" rel="noopener noreferrer"&gt;github.com/sangharshadhyeta/Strata-HotRod&lt;/a&gt;. If you run it on different hardware, I would like your numbers, good or bad. The repo has a short guide for how to report them.&lt;/p&gt;

</description>
      <category>llm</category>
      <category>opensource</category>
      <category>cuda</category>
      <category>machinelearning</category>
    </item>
  </channel>
</rss>
