How does dropless MoE dispatch differ from capacity-factor token dropping?
Same topic, related formats. Practice these next.
Same topic, related formats. Practice these next.
How does dropless MoE dispatch differ from capacity-factor token dropping during training?
Capacity-factor MoE drops overflow tokens when expert buffers fill; dropless MoE redistributes or reschedules so every routed token gets FFN compute, trading scheduling complexity for zero skips.
Capacity-factor routing is like a restaurant that seats only 10 people per chef, when an 11th order arrives, it goes out without the special sauce (token skips FFN, keeps residual). Dropless MoE is the manager who rearranges orders, opens overflow prep stations, or batches smarter so nobody misses their dish, harder to run the kitchen, but no customer leaves without the full meal.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.
Everything important, quickly.
6 min: capacity factor drops vs dropless dispatch, quality impact, and training systems tradeoffs.
Real products, models, and research that use this idea.
What an interviewer would ask next. Try answering before peeking at the approach.
Red flags and common mistakes that signal junior thinking. Click to expand.
Assuming dropless MoE eliminates all routing imbalance, it eliminates token drops, not necessarily perfectly even expert load.
The night-before-the-interview bullets. Scan these on the way to the call.
Primary sources. Skim if you want the original framing.