Olmix: Principled Data Mixing for LLMs
- Olmix is a principled framework for data mixing in LLM training, integrating offline configuration, optimization, and mixture reuse for robust performance.
- It systematically explores key design axes—such as proxy model size, swarm size, and regression granularity—to achieve state-of-the-art bits-per-byte metrics.
- Olmix employs efficient mixture reuse algorithms that adapt to evolving domains, reducing proxy runs by up to 74% while maintaining high model utility.
Olmix is a principled framework for data mixing in the training and continual development of large LMs under evolving domain sets and practical data constraints. It encompasses both a systematic study of the offline data mixing configuration space and a suite of algorithms for efficient mixture recomputation as datasets are added, removed, or revised throughout real-world LM development cycles (Chen et al., 12 Feb 2026).
1. Formal Definition and Problem Setup
Let the domain set be , where each domain contains available tokens. A mixture is a probability vector
specifying that tokens from are used when training for tokens total. An LM of size parameters trained for tokens on mixture is denoted 0. For 1 downstream tasks, the 2-th task is evaluated via the bits-per-byte (BPB) metric
3
with lower values indicating better performance. The data mixing objective is to find
4
In data-constrained settings, a repetition bound 5 is imposed such that
6
This constraint prevents excessive resampling from low-resource domains, addressing overfitting and maintaining data diversity.
2. Offline Mixing Schema and Configuration Space
Olmix builds on a three-step offline mixing schema: Swarm 7 Regression 8 Optimization. The configuration space is parameterized along seven key design axes, each empirically studied:
- Proxy model size (9): Proxy LMs with 0 parameters are required to achieve Spearman 1 correlation with full-scale (1B) models. 2-parameter proxies yield only 3.
- Swarm size 4 vs. domain count 5: Error in the mixing objective collapses when 6; empirically, 7 suffices.
- Swarm distribution 8: Sparse swarms (allowing 9) benefit topic-level domains by uncovering exclusion, while dense swarms suit source-level domains. Dirichlet priors centered on the natural distribution 0 proved robust; uninformative priors degraded performance.
- Regression family 1: Tested surrogates include LightGBM, Gaussian Process, BiMix, AutoScale, and log-linear. The per-task log-linear model
2
yields the highest Pearson correlation (3 at 4) and best downstream BPB.
- Regression granularity: Fitting per-task surrogates (one model per downstream task) achieves the best fit (5) and BPB (0.765 vs. 0.777 per-family, 0.774 aggregated).
- Data repetition constraints: Constraints 6 are enforced solely in the optimization step (7 is typical), rather than during swarm construction. Constraining the swarm degrades performance, while unconstrained swarms plus constrained optimization maintain efficacy.
- Optimization solver: Mixture optimization minimizes
8
subject to the repetition bounds, using CVXPY with a Kullback-Leibler (KL) penalty (9). This regularization mitigates overfitting to the regression surrogate.
These choices form the OlmixBase method, which achieves state-of-the-art results on rigorous BPB benchmarks.
3. Key Empirical Insights
Empirical studies underpin Olmix's recommendations for data mixing in LM training:
- Proxy LMs with 0 parameters at 1 Chinchilla scaling reliably transfer mixing strategies to 1B-parameter models.
- Swarm sample complexity is linear in the number of domains, with 2 sufficient for error minimization.
- Domain granularity (topic or source) informs whether to use sparse or dense swarm priors.
- Per-task log-linear regression achieves average BPB = 0.765; LightGBM and BiMix trail at 0.775 and 0.778, respectively.
- Enforcing repetition bounds in the optimization only allows for higher utility mixes and steadier performance.
- Mixes optimized with a small KL penalty (3) outperform pure convex solvers by reducing over-optimization risk.
4. Mixture Reuse Under Evolving Domains
Olmix introduces algorithms for efficient mixture recomputation when domains change. Rather than re-running the entire offline schema (4 proxy runs for updated 5), mixture reuse freezes weights for unaffected domains and optimizes for new/affected domains only. Partition 6, prescribing
7
with a collapsed mixture 8, 9. Sampling 0 runs in this reduced space and expanding to 1 via 2, one fits per-task log-linear surrogates and optimizes 3 with repetition and KL constraints. PartialMixtureReuse recomputes a superset of old domains to further control coupling, with corresponding complexity.
| Reuse Method | Proxy Runs per Update | Performance (% BPB improvement vs. natural) |
|---|---|---|
| Full Recompute | 832 | +12.2 |
| FullMixtureReuse | 216 | +11.6 |
| PartialMixtureReuse | 272 | +12.0 |
| Swarm Reuse | 268 | +11.4 |
Mixture reuse provides 95% of the full recompute's gains while requiring 74% fewer proxy runs. At 6T tokens, FullMixtureReuse achieves 99% of the full recompute’s improvement (Chen et al., 12 Feb 2026).
5. Experimental Evaluation on Realistic Development Pipelines
A five-stage simulation, mirroring OLMo 1→3 development, demonstrates Olmix's utility:
- Initial: 24 topic domains (DCLM).
- Add: +15 programming-language domains.
- Add: +6 STEM corpora (ArXiv, FineMath-3+, PDFs, Wikipedia, AlgebraicStack, Pes2o).
- Revise: Improved PDF processing replaces previous pipeline.
- Remove/Partition: Drop AlgebraicStack; split PDFs into 21 finer topics (final 4).
1B-parameter OLMo2 LMs are trained for 5B tokens per stage, evaluated on 6 downstream tasks (math, codegen, QA, commonsense), and measured in BPB. The baseline is sampling in proportion to token count (7), and methods compared include OlmixBase, FullMixtureReuse, PartialMixtureReuse, and swarm reuse.
Results reveal that Olmix achieves a 8 speedup in convergence: the best mix reaches the OLMo natural BPB in 9K steps, compared to 0K for naive mixing. All findings are statistically robust across seeds (min–max intervals 1 of mean).
6. Practical Recommendations
Derived from empirical and theoretical analysis, Olmix’s primary recommendations are:
- Use 2M-parameter proxies at 3 Chinchilla scaling for reliable mixture transfer.
- Set swarm size 4 and sample from Dirichlet5; select sparse/dense by domain type.
- Fit per-task log-linear surrogates of the form 6.
- Enforce repetition limits 7 in optimization only (8).
- Solve for the optimal mixture with CVXPY and a KL regularization term (9).
- When domains shift, employ FullMixtureReuse to reduce proxy runs from 0 to 1; with high coupling, use PartialMixtureReuse.
These procedures supply both guidance for initial mixture design and tools for efficient, robust updating as the domain landscape changes and expands.
7. Significance and Context within LLM Training
Olmix empirically establishes principled, statistically robust protocols for data mixing under evolving training corpora—a persistent, under-addressed challenge in LM pipeline management. It systematizes surrogate model choice, regression granularity, sample complexity scaling, domain constraint enforcement, and mixture optimization for optimal downstream task performance. The introduction of mixture reuse methods allows practical, compute-efficient adaptation to new datasets without sacrificing performance. These advances directly address gaps in real-world data curation and model improvement, providing a concrete toolkit for practitioners and researchers training large LMs on dynamic, multi-domain corpora (Chen et al., 12 Feb 2026).