ConMoE: Expert-Pool Consolidation via Prototype Reassignment for MoE Compression
ConMoE is a train-free framework for compressing Mixture-of-Experts (MoE) models that consolidates the expert pool by selecting a smaller set of prototype experts and deterministically remapping original expert calls to them, thereby reducing memory costs without requiring weight updates or post-compression fine-tuning.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you have a massive, high-end restaurant kitchen. This kitchen is designed with a Mixture-of-Experts (MoE) system. Instead of every chef cooking every dish, the kitchen has hundreds of specialized "experts" (chefs). When an order comes in, a "router" (the head waiter) quickly looks at the dish and calls only the top 2 or 3 chefs who are best at that specific task.
The Problem:
Even though only a few chefs cook each dish, the restaurant still has to pay rent, store uniforms, and keep the equipment for all hundreds of chefs in the building. As the restaurant grows (the AI model gets bigger), this storage cost becomes huge, making it expensive and slow to run, even if the chefs aren't all working at once.
The Old Solutions:
Previous methods tried to shrink this kitchen in two ways:
- Pruning: Firing the chefs who seem least busy.
- Merging: Taking two chefs, mixing their recipes together, and creating one "super-chef" with a new, blended style.
The New Solution: ConMoE
The paper introduces ConMoE, which takes a different approach. Instead of firing chefs or blending their recipes, ConMoE says: "Let's keep a smaller, curated team of our best original chefs, and simply tell the head waiter to send orders to them instead."
Here is how it works, using everyday analogies:
1. The "Prototype" Team (The Star Chefs)
ConMoE looks at all the original chefs and picks a smaller group to be the "Prototypes." These are the original, unmodified chefs who are kept on staff.
- How they are chosen: The system checks two things:
- Contribution: Who actually gets called the most and does the best work?
- Replaceability: Who is unique? If we lose Chef A, is there anyone else who can do exactly what they do? If Chef A is unique, they stay. If Chef B is very similar to Chef C, Chef B might be let go.
2. The "Remapping" (The New Menu)
Once the smaller team of "Prototype" chefs is selected, ConMoE creates a deterministic map (a strict rulebook).
- If the original head waiter wanted to call "Chef #42," the rulebook says, "Actually, send that order to Prototype Chef #5 instead."
- If the waiter wanted to call "Chef #99," the rulebook says, "Send that to Prototype Chef #5 as well."
- Crucially: The chefs themselves don't change. They don't learn new recipes, and they don't blend their styles. They are just reused. The "router" (head waiter) doesn't need to be retrained; it just follows the new map.
3. The "Local Neighborhood" Rule
The paper found that you can't just pick any chef from the whole building to replace another.
- The Analogy: A chef on the 1st floor (early layers of the AI) does very different work than a chef on the 50th floor (deep layers). They aren't interchangeable.
- The Solution: ConMoE only allows chefs to be swapped with others in their "local neighborhood" (a few floors up or down). This ensures the replacement chef actually understands the context of the order.
Why is this better?
- No Re-training: You don't need to teach the chefs new tricks (no "fine-tuning"). You just change the phone directory.
- Stability: Because the chefs aren't blended or altered, their original skills remain intact.
- Results: The paper tested this on three different large AI models. They found that ConMoE performed just as well as (and sometimes better than) the methods that fire chefs or blend their recipes, while keeping the system much simpler.
The Catch (Limitations)
- It needs a "Menu" to read: The system needs a small amount of sample text (calibration data) to figure out which chefs are the stars and which are the backups.
- Local only: You can't swap a chef from the basement with one from the penthouse; they do different jobs.
- Storage Reality: While the logical number of chefs is smaller, to actually save physical storage space, the restaurant needs a special way to store the building so that multiple "slots" point to the same physical chef.
In short: ConMoE is like keeping a smaller, elite team of your original experts and simply redirecting all the work to them, rather than firing people or trying to create new "hybrid" experts. It's a smart, no-training-required way to shrink big AI models.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.