<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Model Routing on Nalar</title>
    <link>https://nalar.dev/tags/model-routing/</link>
    <description>Recent content in Model Routing on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 12 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/model-routing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Control Expert Routing in Mixture-of-Experts Models</title>
      <link>https://nalar.dev/control-expert-routing-in-mixture-of-experts-models/</link>
      <pubDate>Sat, 12 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/control-expert-routing-in-mixture-of-experts-models/</guid>
      <description>&lt;p&gt;A mixture-of-experts layer can contain far more parameters than it evaluates for each token. A router scores a set of experts, selects a small subset, and sends each token only to those selected computation paths. The parameter count can grow without making every token execute every expert.&lt;/p&gt;&#xA;&lt;p&gt;That sparse structure creates a separate systems problem: the router decides where computation lands. Two models with the same experts and the same nominal top-k routing can have very different behavior if one spreads tokens across experts and the other concentrates them on a few paths.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
