Fabian Schaipp

539 posts

Fabian Schaipp banner
Fabian Schaipp

Fabian Schaipp

@FSchaipp

working on optimization for machine learning. currently postdoc @inria_paris.

Paris, France Katılım Temmuz 2020
764 Takip Edilen1.3K Takipçiler
Sabitlenmiş Tweet
Fabian Schaipp
Fabian Schaipp@FSchaipp·
very nice paper finding that Muon & SOAP improve training of models for molecular simulations #ICML2026
Fabian Schaipp tweet media
English
0
2
28
2K
Fabian Schaipp retweetledi
Josephine Parquet
Josephine Parquet@josephinePqt1·
🎬 Field Notes: is more data always better? Physical AI is booming, and so are the data providers feeding it. But what actually makes a robot smarter? Awesome to chat with @fabinsch1, researcher at @inria who just presented his thesis in policy learning for robotics. 🧵
English
4
4
28
3.2K
Fabian Schaipp
Fabian Schaipp@FSchaipp·
I will be at ICML from Wednesday, happy to chat on this! 🇰🇷
English
0
1
5
198
Fabian Schaipp
Fabian Schaipp@FSchaipp·
Why would you want to do this? 1) With our law, you get the correct scaling for the optimal batch size with two/three batch sizes per sweep 2) You can also derive scaling laws for *suboptimal* batch size intervals (e.g. which batch sizes waste at most 5% of compute)
Fabian Schaipp tweet mediaFabian Schaipp tweet media
English
1
1
3
336
Fabian Schaipp
Fabian Schaipp@FSchaipp·
How to scale the batch size in LLM pretraining? New paper on a scaling law that splits token budget D into training steps and batch size. 💺 arxiv.org/abs/2607.01487
Fabian Schaipp tweet media
English
3
13
97
7.7K
Antonio Orvieto
Antonio Orvieto@orvieto_antonio·
Hot question: how should we allocate tokens: more steps or bigger batches? How big is "too big" for our batches? @FSchaipp proposes to fit a simple **three**-term law: L(N,M,K)= E + A·N⁻ᵅ + B·M⁻ᵝ + C·K⁻ᵞ, where M is the batch size in tokens and K is the number of training steps. Compared to works that fit batch-size laws directly, here batch size enters the loss law itself, so optimal and critical batch sizes are derived rather than being fit separately. Since D = MK (tokens), the law predicts an optimal batch size M* ∝ D^(γ/(β + γ)). paper: arxiv.org/pdf/2607.01487
Antonio Orvieto tweet media
English
4
12
119
8.6K
Fabian Schaipp
Fabian Schaipp@FSchaipp·
@cjmaddison @orvieto_antonio will have a look. the batch size and steps terms are essentially resembling the structure of convergence bounds (details in the paper)
English
1
0
1
61
Hiroki Naganuma
Hiroki Naganuma@_Hiroki11x·
Finding 1: the base learning rate matters far more than which schedule family you choose. Takeaway: tune the base LR first, and re-tune it for every shape. Comparing shapes without doing this is how you get misleading results. (4/7)
Hiroki Naganuma tweet media
English
2
1
11
1.4K
Lucas Beyer (bl16)
Lucas Beyer (bl16)@giffmana·
This is the natural continuation of this group's previous several works on optimization, and I really like their style. A lot of experiments to look at all possible details. As opposed to a wall of theory and then one single experiment with untuned baselines.
Alex Hägele@haeggee

Our paper is now on arXiv: arxiv.org/abs/2606.25971 Besides all the details and discussions of the broader literature, it also contains lots other experiments that answer some of the questions we have already received. For example:

English
6
46
439
49.8K
Fabian Schaipp
Fabian Schaipp@FSchaipp·
awesome blog post! the Apertus project keeps on pushing optimization research for open LLMs.
Alex Hägele@haeggee

New research from our MLO Lab @EPFL: Improving Neural Network Training by Decoupling the Magnitude and Direction of Weight Vectors. Magnitude-Direction Decoupling (MD): a simple optimizer tweak, and what we (currently) think is the right way to train efficiently at scale. 🧵

English
0
5
26
3.9K
George Grigorev
George Grigorev@iamgrigorev·
EMA is such a strong technique for pre-training. You can spend 1.5x more compute and get 0.01 eval loss improvement or just apply EMA at final stages of cooldown and consistently get the same result.
English
4
3
145
19.4K
Fabian Schaipp retweetledi
Antonio Orvieto
Antonio Orvieto@orvieto_antonio·
Judging optimizer gaps by looking only at language modeling with a fixed batch size is dangerous: one gets only 1/2 of the story. @orientino_ and @ruuustem_10 went beyond. Turns out that for every model, task, and data, there is always a setup where Adam > SGD. 🧵
Antonio Orvieto tweet media
English
2
15
73
10.2K
Dimitris Papailiopoulos
Dimitris Papailiopoulos@DimitrisPapail·
taught grandpa SGD to speedrun GPT tonight 2x slower than Muon. We are 0.10 nats from god and $300 of runpod credits poorer... yet doing the single most dangerous thing I can: leaving the agents (codex and CC with fumble) run overnight 🫡 see wassup tomorrow. either 3.28 at 550s or go home with 300$ less
Dimitris Papailiopoulos tweet mediaDimitris Papailiopoulos tweet media
Dimitris Papailiopoulos@DimitrisPapail

We may be only 250$ (aka 10 hours) away from the machine god uber optimizing SGD to close the gap

English
7
3
53
11.9K
Rustem
Rustem@ruuustem_10·
@FSchaipp Great work! With @orvieto_antonio @n_ajroldi we most of the times observed that NGN step size is more stable than SPS. Interesting to see that it’s also somehow suggested by your theory. Can the same be done for convex-smooth losses?
English
1
0
2
290
Fabian Schaipp
Fabian Schaipp@FSchaipp·
"It's easier to tune the LR for method A than for B." We tried to formalize this for model-based stochastic optimization methods. We find a key quantity, called stability index, that describes how stable a (weakly) convex bound is as a function of LR. 📚arxiv.org/abs/2602.09842
Fabian Schaipp tweet media
English
3
9
71
10.2K