<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Archive on matrix-multiply</title><link>https://matrix-multiply.com/posts/</link><description>Recent content in Archive on matrix-multiply</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 30 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://matrix-multiply.com/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>Benchmarking Trillion-Parameter Open Models Without Fooling Yourself</title><link>https://matrix-multiply.com/posts/benchmarking-without-fooling-yourself/</link><pubDate>Sun, 30 Aug 2026 00:00:00 +0000</pubDate><guid>https://matrix-multiply.com/posts/benchmarking-without-fooling-yourself/</guid><description>&lt;p&gt;We ran Kimi K3 and DeepSeek V4 (Pro and Flash) head-to-head on a hard-benchmark suite — same harness, same serving stack, same hardware, back to back. The scores are below, but the scores are honestly the less useful half of this post. The useful half is the list of ways the numbers were nearly wrong.&lt;/p&gt;&#10;&lt;h2 id="the-setup"&gt;The setup&lt;/h2&gt;&#10;&lt;p&gt;Everything ran on one 8×B300 node (tensor-parallel 8) with vLLM, driven by lm-eval plus custom harnesses for AIME-25 and BBEH. Identical prompts, budgets, and scoring for all three models. We deliberately dropped saturated benchmarks (GSM8K, MMLU, ARC — everything scores in the high 90s or clusters within noise) and kept rows with headroom:&lt;/p&gt;</description></item><item><title>896 Experts, None Dead: What MoE Load Actually Looks Like at Token Level</title><link>https://matrix-multiply.com/posts/896-experts-none-dead/</link><pubDate>Fri, 28 Aug 2026 00:00:00 +0000</pubDate><guid>https://matrix-multiply.com/posts/896-experts-none-dead/</guid><description>&lt;p&gt;There&amp;rsquo;s a seductive idea floating around MoE deployment discussions: with huge scale-up domains coming (NVL72 and beyond), why not give every expert its own accelerator? One expert, one chip, perfect disaggregation.&lt;/p&gt;&#10;&lt;p&gt;We measured what that would actually do, using Kimi K3 — 896 routed experts per MoE layer, 92 such layers, top-16 routing — served on an 8×B300 node. A small patch in the serving stack recorded a per-layer histogram of every expert selection across a mixed workload (math, knowledge, and code benchmarks). Here&amp;rsquo;s what the router&amp;rsquo;s traffic really looks like.&lt;/p&gt;</description></item><item><title>The Free Lunch That Wasn't (Part 2: Ten Seeds Later)</title><link>https://matrix-multiply.com/posts/the-free-lunch-that-wasnt/</link><pubDate>Wed, 26 Aug 2026 00:00:00 +0000</pubDate><guid>https://matrix-multiply.com/posts/the-free-lunch-that-wasnt/</guid><description>&lt;p&gt;&lt;em&gt;This is part 2 of two. &lt;a href="https://matrix-multiply.com/posts/kimi-k3-expert-routing-eval/"&gt;Part 1&lt;/a&gt; set up the&#10;experiment and ended on a +5.5 point HumanEval gain from routing to 32 experts&#10;instead of 16, flagged as single-seed and unbelieved. This post is the&#10;replication.&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;To recap the premise: Kimi K3 is a 1.56 TB, 896-expert mixture-of-experts model.&#10;For every token, at every one of its 61 MoE layers, a router picks 16 experts&#10;out of 896 and blends their outputs. That &lt;code&gt;top-k = 16&lt;/code&gt; is a training-time&#10;hyperparameter, and &lt;strong&gt;you can override it at inference time&lt;/strong&gt; with a ~10-line&#10;patch to the serving stack. No retraining, no fine-tuning.&lt;/p&gt;</description></item><item><title>Does Kimi K3 Want More Experts? (Part 1: The Tempting Result)</title><link>https://matrix-multiply.com/posts/kimi-k3-expert-routing-eval/</link><pubDate>Sat, 15 Aug 2026 00:00:00 +0000</pubDate><guid>https://matrix-multiply.com/posts/kimi-k3-expert-routing-eval/</guid><description>&lt;p&gt;&lt;em&gt;This is part 1 of two. It ends with a result that looks like a free lunch.&#10;&lt;a href="https://matrix-multiply.com/posts/the-free-lunch-that-wasnt/"&gt;Part 2&lt;/a&gt; spends ten seeds and a router&#10;instrumentation pass finding out whether it was real. It wasn&amp;rsquo;t.&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;Kimi K3 activates 16 of its 896 experts per token. That number comes from&#10;training; nothing forces you to keep it at inference time. The router scores&#10;experts, and how many of those scores you act on is a runtime choice.&lt;/p&gt;</description></item></channel></rss>