<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>NVFP4 on Matt Suiche</title><link>https://www.msuiche.com/tags/nvfp4/</link><description>Recent content in NVFP4 on Matt Suiche</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 04 Sep 2026 23:00:00 +0200</lastBuildDate><atom:link href="https://www.msuiche.com/tags/nvfp4/index.xml" rel="self" type="application/rss+xml"/><item><title>Inkling on Two DGX Sparks: The Only vLLM Lane, and the Two Walls Behind It</title><link>https://www.msuiche.com/posts/inkling-on-two-dgx-sparks-the-only-vllm-lane-and-the-two-walls-behind-it/</link><pubDate>Fri, 04 Sep 2026 23:00:00 +0200</pubDate><guid>https://www.msuiche.com/posts/inkling-on-two-dgx-sparks-the-only-vllm-lane-and-the-two-walls-behind-it/</guid><description>&lt;p&gt;Thinking Machines shipped &lt;a href="https://thinkingmachines.ai/news/inkling-small/" target="_blank" rel="noopener"&gt;Inkling-Small&lt;/a&gt; at the end of July: a ~300B-total,
~10B-active hybrid MoE (short-conv plus relative-bias attention), natively
multimodal, 1M context, and - the part that matters for homelab hardware -
released as NVFP4 from day one. 170.7 GB of weights. Two DGX Sparks hold 243 GB
of unified memory. You can see where this is going.&lt;/p&gt;
&lt;p&gt;For five weeks, though, every Spark recipe for it -
&lt;a href="https://github.com/drowzeys/keys-1M-CTX-Inkling-Small-NVFP4-Dspark-NVFP4-KV-Cache-SGlang-SM121-optimized-on-Two-DGX-Sparks" target="_blank" rel="noopener"&gt;drowzeys&amp;rsquo; champion image&lt;/a&gt;,
&lt;a href="https://github.com/MiaAI-Lab/Inkling-Small-NVFP4-Dual-DGX-Sparks" target="_blank" rel="noopener"&gt;MiaAI&amp;rsquo;s wrapper&lt;/a&gt;,
and the half-dozen forks - ran on &lt;strong&gt;SGLang&lt;/strong&gt; with a custom-baked image, for a
simple reason: SGLang had Inkling support in early August, and vLLM only gained
it this week, in v0.28.0. The engine we build everything on could not even load
the model before Monday.&lt;/p&gt;</description></item><item><title>Autoresearch: Sticky Refusals, Free Speculative Decoding, and the Invisible Quantisation Cliff</title><link>https://www.msuiche.com/posts/autoresearch-sticky-refusals-free-speculative-decoding-and-the-invisible-quantisation-cliff/</link><pubDate>Thu, 03 Sep 2026 00:00:00 +0200</pubDate><guid>https://www.msuiche.com/posts/autoresearch-sticky-refusals-free-speculative-decoding-and-the-invisible-quantisation-cliff/</guid><description>&lt;p&gt;This is the follow-up to the &lt;a href="https://www.msuiche.com/posts/autoresearch-abliteration-without-redistributing-the-model/"&gt;projection-steering post&lt;/a&gt;:
two more weeks, five model families, and a pile of measurements that killed
several of my own assumptions. The short version is that the GLP approach, ship the
&lt;em&gt;difference&lt;/em&gt;, not the model, now covers seven checkpoints from five vendors
(DeepSeek, Qwen, Z.ai, Thinking Machines, Tencent), and the
interesting findings are no longer &amp;ldquo;it works&amp;rdquo; but &lt;em&gt;where it behaves differently&lt;/em&gt;,
&lt;em&gt;what it composes with&lt;/em&gt;, and, the new thread, &lt;em&gt;what it breaks that isn&amp;rsquo;t refusal&lt;/em&gt;.&lt;/p&gt;</description></item></channel></rss>