Summary
In this paper, the authors study the training dynamics of small language models (i.e., models ranging from 1.2-2.4 billion parameters). Specifically, they focus on what they call “model wind tunnel” experiments. This involves training and studying model developing in 3 parts: 1) hyper-parameter selection (mostly focusing on network width and depth scaling parameters); 2) optimal batch sizing and; 3) learning rate scheduling. The most novel part of their work seems to be in the last part related to the development of what they call “warmup stable decay” (WSD), their learning rating scheduler that is conducive to continuous training and training without a fixed token length.
These experiments above lead to the following results (centering around experiments on C4): a new empirical bound on the optimal relationship between batch size and C4 loss that helps to minimize both token amount and loss (reported at the end of Section 3.2). Compelling empirical results on the efficacy of their WSD scheduling method (which breaks the scheduler into 3 stages: warmup, stable and decay stages, informed by systematic experiments they performed on cosine-warmup and its sensitivity to various step parameters); in particular, they report impressive losses with very small models on C4 (Figures 5 and 6).
Based on these insights, they then train a family of small language models called miniCPM. Their training pipeline is comprehensive, ranging from full pre-training (at the scale of trillion of tokens using aggregations of multilingual publicly available pre-training corpora), to supervised instruction tuning and DPO-style alignment. They also tested across different architectures (e.g., MoE derivates and long-context versions of their models). The main novelty in this pre-training setting is the introduction of SFT data into the decay stage of their pre-training and scheduler (while I know this has become popular d recently, I worry that this makes their models have an unfair advantage over some of the other models they are comparing against; more about this below).
The results are impressive and, after looking through the details in the appendix, I was happy to see that not only were all the model comparisons produced by the authors themselves using a single tool, but that performance reported is based on each model’s best performance either through perplexity-based evaluation or direct generation. While I initially found Table 2 to be a bit confusing (highlighting would be very helpful here!), I was particularly struck by the relative average performance of 13-40B models against MiniCPM-2.4B.
Reasons to accept
- A very careful study on optimal model training strategies for small LLMs, which is an important area of research that, as the authors convincingly argue, touches on important issues related to practical deployment of LMs.
- The paper is very easy to read and I found all the experiments to be well motivated. I believe that their experiments will motivate further research in this area.
- A new suite of small LMs that I think will be used and embraced by the community (the question of whether these models will be released was not addressed; see questions below).
Reasons to reject
- My main concern centers around the introduction of instruction data into the pre-training stage, and whether this makes the comparisons fair to many of the models in Table 2 (models that presumably didn't do this). While I don't think that this is grounds for a rejection, I would like to see the authors motivate and address this. If there were any ablations on this (maybe that I would missed), it would be helpful to report. (Given that this was done in the most recent OLMO 1.7 model, this might be worthwhile to compare against)
Questions to authors
- Will you models be released, and if so under what license?
- I was surprised not to see (unless I missed it) details about the the particular optimizer you used. Can you clarify this?
- I was surprised to that your SFT stage includes training on 6 billion tokens. Did you report what sources you used?
- you called the alignment stage RLHF, but as far as I can tell, you weren't using RL, because you were training with DPO, right? Please clarify.
other comments
- The caption is Table 1 is very hard to read, please revise.