Back to Feed
Training & Fine-Tuning / Benchmarks & Evals

Optimizing Mixture of Experts Diffusion Models

Original: LLaDA MoE v2: Scaling Mixture-of-Experts Diffusion Language Models

Listen to the summary

Uses a voice available on your device

Audio options
On this page

Key Takeaways

  • Established formal scaling laws for Mixture-of-Experts (MoE) architectures, which use only a subset of model parameters per inference request, by testing models from 158M to 3.6B parameters.
  • The LLaDA MoE v2 (30B-A3B) achieves performance parity with Qwen3 while requiring only 65% of the pretraining tokens.
  • Discovered that the optimal shared-expert ratio, which defines the portion of the model parameters active for every input, is consistently 33.3% across compute scales.
  • The instruction-tuned version of LLaDA MoE v2 outperforms SDAR Chat across seven of eight reasoning and coding benchmarks.

Summary & Methodology Analysis

The researchers addressed the lack of clear scaling behaviors for Mixture-of-Experts diffusion language models by performing systematic hyperparameter searches. They utilized models ranging from 158M to 3.6B parameters to fit scaling laws for token batch sizes and learning rates relative to the compute budget. This methodology included IsoFLOP analysis, where they swept activated computation against training data across a massive range of 10^17 to 10^20 training FLOPs to define how architecture choices like expert granularity and shared-expert ratios influence performance at fixed costs.

Based on these discovered laws, they trained the LLaDA MoE v2 model, a 30B parameter architecture with 3B activated parameters (30B-A3B), from scratch on 23.5T tokens. The model architecture relies on an optimal 33.3% shared-expert ratio. Following pretraining, the model underwent supervised fine-tuning for three epochs on 7M instruction-response examples to optimize its performance for chat-like interactions and specific reasoning tasks.

While the resulting model demonstrates high efficiency, the study faces a significant architectural limitation regarding model analysis. The authors did not examine how the various scaling dimensions, such as expert granularity and shared-expert ratios, interact with one another because the experiments were performed as isolated, separate sweeps. This means the identified scaling laws are based on independent optimization rather than a holistic exploration of multi-dimensional interactions.

Interactive System Flowchart

Click diagram to expand and zoom

Cross-Examination & FAQs

A deeper dive clarifying mechanics, constraints, and baseline evaluations.

Q1. What is the primary contribution of this research?

The paper defines scaling laws for Mixture-of-Experts diffusion language models to determine the best architectural designs and compute allocations.

Q2. What is the LLaDA MoE v2 model?

It is a 30B parameter diffusion language model with 3B activated parameters that was trained from scratch using the newly discovered scaling laws.

Q3. How does this model compare to existing solutions?

It matches Qwen3 performance while using 65% fewer pretraining tokens and outperforms SDAR Chat on seven of eight reasoning and coding benchmarks.

Q4. What range of model scales did the researchers test?

They performed hyperparameter searches across model scales ranging from 158M to 3.6B parameters.

Q5. What is the optimal shared-expert ratio?

The researchers found that the optimal shared-expert ratio remains constant at 33.3% across all studied compute scales.

Q6. How was the model tuned for instruction-following?

They applied supervised fine-tuning for three epochs on 7M instruction-response examples.

Q7. What is the primary limitation of this study?

The study does not examine how the different scaling dimensions interact with one another because the experiments were conducted separately.

Q8. What training data volume was used for LLaDA MoE v2?

The model was trained on 23.5 trillion tokens.

Q9. Does this paper specify the hardware requirements for inference?

No, the paper does not specify hardware requirements for running the model.