惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

N
Netflix TechBlog - Medium
I
InfoQ
Engineering at Meta
Engineering at Meta
Jina AI
Jina AI
Recent Announcements
Recent Announcements
T
The Blog of Author Tim Ferriss
P
Proofpoint News Feed
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
D
Docker
Microsoft Security Blog
Microsoft Security Blog
宝玉的分享
宝玉的分享
Last Week in AI
Last Week in AI
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
GbyAI
GbyAI
博客园 - Franky
博客园 - 聂微东
Microsoft Azure Blog
Microsoft Azure Blog
博客园 - 叶小钗
酷 壳 – CoolShell
酷 壳 – CoolShell
B
Blog RSS Feed
WordPress大学
WordPress大学
MyScale Blog
MyScale Blog
月光博客
月光博客
罗磊的独立博客

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Shared expert pool reduces parameters while maintaining p...
Papers Mache · 2026-05-15 · via DEV Community

Papers Mache

Conventional mixture‑of‑experts designs hand each transformer layer its own private expert set, causing the total expert parameter count to swell linearly with depth. Recent work shows that a single, globally shared pool of experts can deliver comparable predictive quality while dramatically curtailing that budget.

The dominant paradigm has treated depth scaling and expert capacity as inseparable: every new layer brings a fresh collection of feed‑forward sub‑networks, and the routing logic merely picks the top‑k among them. This architecture simplifies implementation but forces a strict coupling between model depth and the number of learnable expert parameters, even though earlier analyses hinted that many layers rely on overlapping knowledge.

UniPool breaks the coupling by replacing per‑layer ownership with one shared pool that all routers draw from. Training remains stable thanks to a pool‑level auxiliary loss that balances utilization at the granularity where parameters are actually owned: the global expert pool. The paper reports, "The improvement from UniPool over vanilla MoE is consistent at all five scales, with validation loss reductions of 0.0288 (182M), 0.0346 (469M), 0.0308 (650M), 0.0386 (830M), and 0.0172 (978M)" [1]. Moreover, “reduced‑pool UniPool variants using only 41.6%–66.7% of the vanilla expert‑parameter budget match or outperform layer‑wise MoE at the tested scales” [1], demonstrating that expert parameters need not grow linearly with depth.

MASCing tackles a different, but equally practical, problem: the safety of MoE inference. By training an LSTM‑based surrogate that models cross‑layer routing dependencies, the framework learns a steering matrix that identifies behavior‑relevant expert circuits. At inference time it injects “steering masks” into the routing gates, overriding the default expert selection without any retraining. The authors note, "MASCing uses an LSTM‑based surrogate model to capture cross‑layer routing dependencies and map routing logits to downstream behaviors. It then optimizes a steering matrix to identify behavior‑relevant expert circuits and, at inference time, applies steering masks to the routing gates to override expert selection" [2]. In the adversarial jailbreak benchmark, unsteered models defended successfully only 52.5% of the time on average, whereas “Applying MASCing yields a substantial and consistent improvement across all tested MoE models, raising the average defense success rate to 83.9%” [2].

The findings leave several open questions. UniPool’s experiments are limited to LLaMA‑style backbones trained on 30 B tokens from the Pile; it remains unclear whether the same sublinear expert budget holds for encoder‑only transformers, multimodal models, or data regimes with markedly different token distributions. The auxiliary loss and NormRouter components introduce extra hyper‑parameters that may require careful tuning on new hardware stacks. MASCing, while impressive, depends on a surrogate that approximates routing dynamics; its efficacy on proprietary, larger‑scale MoEs or under distribution shifts has not been demonstrated, and the steering masks could interact unpredictably with future routing innovations.

For engineers looking to shave expert parameters without sacrificing loss, swapping the layerwise expert modules for a single shared pool and adding the pool‑level balancing loss is a concrete first step; the authors release ready‑to‑run scripts that cover five model sizes, so you can prototype the change on existing training pipelines. When safety requirements evolve, you can generate a steering mask for the new objective and plug it into the inference graph, gaining a sizable jailbreak‑defense boost without a costly fine‑tune. Before committing, benchmark the shared‑pool model against a vanilla MoE on your own validation set and measure any latency impact of the auxiliary loss and mask application. If the trade‑off is favorable, the combined modular routing approach offers a practical path to cheaper, more controllable large‑scale models.

References

  1. UniPool: A Globally Shared Expert Pool for Mixture-of-Experts
  2. MASCing: Configurable Mixture-of-Experts Behavior via Activation Steering Masks