Papers › Efficient Online Data Mixing For Language Model Pre-Training

Efficient Online Data Mixing For Language Model Pre-Training

5 Dec 2023arXiv:2312.02406archive 2025-07-28

Alon Albalak, Liangming Pan, Colin Raffel, William Yang Wang

The data used to pretrain large language models has a decisive impact on a model's downstream performance, which has led to a large body of work on data selection methods that aim to automatically determine the most suitable data to use for pretraining. Existing data selection methods suffer from slow and computationally expensive processes, a problem amplified by the increasing size of models and of pretraining datasets. Data mixing, on the other hand, reduces the complexity of data selection by grouping data points together and determining sampling probabilities across entire groups. However, data mixing proportions are typically fixed before training and therefore cannot adapt to changing training dynamics. To address these limitations, we develop an efficient algorithm for Online Data Mixing (ODM) that combines elements from both data selection and data mixing. Based on multi-armed bandit algorithms, our online approach optimizes the data mixing proportions during training. Remarkably, our method trains a model that reaches the final perplexity of the next best method with 19% fewer training iterations, and improves performance on the 5-shot MMLU benchmark by 1.9% relative accuracy, while adding negligible wall-clock time during pretraining.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 9 code samples harvested from 1 repository linked to this paper: 7 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 1 honoured, 0 violated, 1 with no contract checked; 5 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 5 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: community (archive-listed): 9 samples from 1 repository, 7 ran (2 with no instrument failure; 5 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

alon-albalak/online-data-mixing mentioned on GitHubpytorchApache-2.0Syntology: 9 samples, 7 ran (5 instrument-failed) · 2 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

9 samples harvested: 7 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 1 honoured, 0 violated, 1 with no contract checked; 5 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · honoured contract
5ran · our draft was wrong
1ran
2unverified

Licence: 9 of the 9 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from alon-albalak/online-data-mixing. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. For 1 sample that ran, the graph records a signature this page does not show: an argument's recorded type or element kind is a printout of an object in Syntology's harness (such as a mock object, a class or a pandas printout), not the type of an input, so it does not describe the call's shape. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

alon-albalak/online-data-mixing community (archive-listed) 9 samples, 7 ran (5 instrument-failed) · 2 unverified
code in 14 papers bigram_model.py ran · honoured contract Apache-2.0 recorded; this copy not marked cleared · pointer only · 01edd35282158f9c · report fixture: returned int · level recorded 2026-09-24
data_file_path in 9 papers bigram_model.py ran · our draft was wrong fingerprinted Apache-2.0 recorded; this copy not marked cleared · pointer only · bdf28f9492a770dc · report fixture: signature prefix_path:str/0/str · returned str · level recorded 2026-09-25
get_flops in 14 papers megatron/logging.py ran Apache-2.0 recorded; this copy not marked cleared · pointer only · 4f686edc1148a835 · report fixture: signature neox_args:MockNeoXArgs/0/?, model:callable/0/?, iter_time_s:float/0/float · returned float · level recorded 2026-09-24
human_readable_flops megatron/logging.py ran · our draft was wrong fingerprinted Apache-2.0 recorded; this copy not marked cleared · pointer only · 32c8c6d61ee207b7 · report fixture: signature num:float/0/float · returned str · level recorded 2026-09-24
index_file_path in 9 papers bigram_model.py ran · our draft was wrong fingerprinted Apache-2.0 recorded; this copy not marked cleared · pointer only · 8b1a74a6db32c163 · report fixture: signature prefix_path:str/0/str · returned str · level recorded 2026-09-25
pairwise in 27 papers configs/gen_docs.py ran · our draft was wrong Apache-2.0 recorded; this copy not marked cleared · pointer only · 50c9c165cf801f59 · report fixture: signature iterable:list/1/int · returned zip_longest · level recorded 2026-09-25
to_md in 6 papers configs/gen_docs.py ran · our draft was wrong Apache-2.0 recorded; this copy not marked cleared · pointer only · 64dd872a8ac47294 · report fixture: signature docs:dict/0/?, intro_str:str/0/str · returned str · level recorded 2026-09-25
broadcast_data megatron/mpu/data.py unverified Apache-2.0 recorded; this copy not marked cleared · pointer only · ec62b348d91f2d73 · report
get_docs in 6 papers configs/gen_docs.py unverified Apache-2.0 recorded; this copy not marked cleared · pointer only · 750d7ac5c014981c · report

Tasks

Language ModelingLanguage ModellingMMLU

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections