Introducing Olmo-core 3: Open, scalable training infrastructure for large MoEs

Hugging Face Blog ·

Kyle Wiggers’ post on Hugging Face reports Ai2’s own Olmo-core 3 benchmarks. It describes scaling the expert pool with roughly fixed active parameters, a preliminary eight-GPU throughput comparison with the earlier stack, and a controlled MXFP8 comparison with BF16. These are reported benchmark results from the post, not independent measurements. Read 3 viewpoints with supporting evidence and source links.

Understand this piece

3 key points

Synthesis

  1. Maintaining throughput while scaling expert count

    The post reports that increasing the expert pool from 8 to 128 while selecting only four experts per token kept active parameters per token roughly fixed at ~3.2B; total parameter capacity grew from 4.6B to 47B with less than 5% drop in training throughput.

    Supporting evidence 1

    Original excerpt

    In one benchmark, we increased the expert pool from 8 to 128 while still selecting only four experts per token – the small units of text a language model processes – keeping the number of active parameters per token roughly fixed at about 3.2B. Total parameter capacity grew from 4.6B to 47B, while training throughput fell by less than 5%.

    Kyle Wiggers · Paragraph 5

    Context

    Olmo-core 3 is built to close that gap.

    Read in source context →

    Continue exploring

    MoE scaling efficiency →
  2. 2.7× throughput gain with DDP-based MoE stack

    The post reports that on eight NVIDIA B300 GPUs, Olmo-core 3’s new distributed data parallelism (DDP)-based MoE training stack achieved 52,000 tokens/sec/GPU versus 19,400 tokens/sec/GPU with the prior FSDP-based implementation — a ~2.7× throughput improvement.

    Supporting evidence 1

    Original excerpt

    In a preliminary test on eight NVIDIA B300 GPUs, a 47-billion-parameter MoE processed 52,000 tokens per second per GPU with the new stack, compared with 19,400 using our earlier implementation—about 2.7× the throughput.

    Kyle Wiggers · Paragraph 11

    Context

    NVIDIA’s Megatron-Core is an established option for training large MoEs. Olmo-core 3 brings an integrated MoE training stack to the framework behind Olmo, with a redesign that improves throughput over our earlier FSDP-based implementation.

    Read in source context →
  3. MXFP8 improves throughput and peak active memory in a controlled B300 benchmark

    The post reports that in a controlled benchmark on four NVIDIA B300 GPUs with uniform expert load, enabling MXFP8 in performance-critical parts increased end-to-end training throughput by ~21% over BF16 baseline and reduced peak active memory from 103 GiB to 95 GiB; most gains came from feed-forward computation and inter-expert data movement, not attention alone.

    Supporting evidence 1

    Original excerpt

    With MXFP8 enabled across the parts of the system where it helped most, training throughput was about 21% higher than with BF16, the higher-precision format we used as our baseline, while peak active memory fell from 103 GiB to 95 GiB. Most of the gain came from feed-forward computation and moving data between experts rather than attention alone.

    Kyle Wiggers · Paragraph 21

    Context

    We measured MXFP8’s effect on end-to-end training throughput in a controlled benchmark on four NVIDIA B300 GPUs, with work distributed uniformly across experts.

    Read in source context →

Key passages3

Attributed passages with the context to verify them. Open the original text to check the source.

training infrastructure performance

2.7× throughput gain with DDP-based MoE stack

Original excerpt

In a preliminary test on eight NVIDIA B300 GPUs, a 47-billion-parameter MoE processed 52,000 tokens per second per GPU with the new stack, compared with 19,400 using our earlier implementation—about 2.7× the throughput.
Context

NVIDIA’s Megatron-Core is an established option for training large MoEs. Olmo-core 3 brings an integrated MoE training stack to the framework behind Olmo, with a redesign that improves throughput over our earlier FSDP-based implementation.

MoE scaling efficiency

Maintaining throughput while scaling expert count

Original excerpt

In one benchmark, we increased the expert pool from 8 to 128 while still selecting only four experts per token – the small units of text a language model processes – keeping the number of active parameters per token roughly fixed at about 3.2B. Total parameter capacity grew from 4.6B to 47B, while training throughput fell by less than 5%.
Context

Olmo-core 3 is built to close that gap.

numerical precision optimization

MXFP8 improves throughput and peak active memory in a controlled B300 benchmark

Original excerpt

With MXFP8 enabled across the parts of the system where it helped most, training throughput was about 21% higher than with BF16, the higher-precision format we used as our baseline, while peak active memory fell from 103 GiB to 95 GiB. Most of the gain came from feed-forward computation and moving data between experts rather than attention alone.
Context

We measured MXFP8’s effect on end-to-end training throughput in a controlled benchmark on four NVIDIA B300 GPUs, with work distributed uniformly across experts.

Source & methodology

These viewpoints are linked to their original sources. Paraphrases are labeled and are not verbatim quotes.

Open transcript or source material (opens in a new tab)Report an issue

Explore these viewpoints by person

Continue with this topic

More sources on topics discussed here. Shared topics do not imply agreement.