apaz (@apaz_cli) header
apaz (@apaz_cli) profile picture

https://teapaw.org/t.co/EYtS07NoX4 Making GPUs go brrr

Hiding in your wifi
Joined July 2019
Photo by apaz (@apaz_cli)Photo by apaz (@apaz_cli)Photo by apaz (@apaz_cli)Photo by apaz (@apaz_cli)Photo by apaz (@apaz_cli)Photo by apaz (@apaz_cli)Photo by apaz (@apaz_cli)Photo by apaz (@apaz_cli)Photo by apaz (@apaz_cli)Photo by apaz (@apaz_cli)
Pinned Tweet
Releasing mlsweep, a sweep scheduler and visualizer for distributed ML training. It aims to make launching runs across groups GPUs frictionless and achieve near feature-parity with wandb. But you can use it with whatever frameworks or loggers you like, wandb included.
4
8
1
52
8,174
I'm actually really confused as to why Anthropic would release the memory wiki findings. Seeing as they were so concerned in the METR report to censor even the name of their agent scaffold. Which undoubtedly uses some similar kind of memory system for grounding and coordination.
wtf this is unreasonably powerful had Opus write a wiki-style memory system for 1017, iterated a bit, and the uplift is honestly spooky. RSI in one Obsidian vault, Yud's nightmare. I cannot see yet how far it goes. I'll need to investigate more
4
5
1
166
12,456
Over the past week or so I've been carefully building a research wiki system too. For exactly the same reasons. I want to let agent swarms run rampant over my research projects, and they need a way to communicate with themselves, and with me. So, Anthropic's notes on wiki memory systems are ABSOLUTELY going to "accelerate other AI developers."
5
2
56
2,959
I did not expect them to just drop a research acceleration gold mine on me for no reason.
9
737
Sharon was one of the few people at AMD I interacted with who gave me hope for the company. This is a great loss for AMD, more than anyone realizes.
I've joined Anthropic! I'm excited to get back to (frontier) research and work on the models that I fell in love with a decade ago. I’m very grateful for my time at @AMD ♥️ Starting with the people: I'm honored to have had the opportunity to work with the one and only @LisaSu! She's an amazing leader, manager, and friend who allowed me so much agency in my work -- they say don't meet your heroes, but she definitely lives up to the pedestal that I've put her on. And thank you to my team: dedicated, resilient folks who've been brave enough to jump on a rocket ship together, in some cases several times to ever ambitious projects. For those who came with me from my startup Lamini - thank you also for bringing your passion, wonder, kindness, and (yes) silliness with me, as we found a home at AMD. And now the work: I built and ran an AI research org that led our frontier lab partnerships, where I served as executive sponsor. We were among the first in the AI research world to take RL kernel optimization really seriously last year, and it showed me that pushing a frontier capability forward takes far fewer people than you’d think (100x, and I'm now updating my priors to 1000x fewer, than just a year ago). That work has also had massive implications for the compute that labs and companies can now use out-of-the-box with models like Claude. That is to say, it’s always time to make some GPUs go brrr.
29
2,202
I think zettelkasten are a very bad abstraction for humans doing research. It takes so much time to wrangle and organize and maintain. Time you could spend on the thing you're actually working on. This logic does not apply to agent swarms.
7
422
Kinda insane that mlsweep's scope has crept from being a tool for making charts, to a fully fledged automated research system. I haven't been talking about it at all. I've just been using it to run my own experiments and build my own infra. But, more updates coming soon.
Releasing mlsweep, a sweep scheduler and visualizer for distributed ML training. It aims to make launching runs across groups GPUs frictionless and achieve near feature-parity with wandb. But you can use it with whatever frameworks or loggers you like, wandb included.
7
338
There have been a bunch of Zeroth Order Optimization research papers recently. I wrote an article digesting them and their mathematical implications. I went a bit overboard. It covers Dust and noise (qlabs), SOMA (@FrancoisChauba1), Async ZO (@BillyHoy1_), and future directions.
3
5
30
1,365
Dust is not just a small improvement over SPSA/ES/EGGROLL/MeZO. It's huge. I'll leave it to the article to discuss why. But the implied (and observed) improvements over weight perturbation are enormous. With that said, the theory still suggests room for improvement.
1
6
245
Reach out to me if you want to talk about zeroth order optimization, or any of the papers cited. It's too big a topic for any individual to tackle alone, and there is strength in community and openness. Blog post: apaz.dev/blog/ZO_Research_Up…
1
3
180
Up at 4am monitoring the research swarm, alas for my sleep schedule
1
5
262
it is honestly quite baffling to me that openai and anthropic still use slack. i expect this will change within the next six months. they could quite clearly build and maintain internal versions that are *more* secure, robust, and featureful with a team of ~10
110
20
16
1,437
503,957
There is very interesting overlap actually between the Dust paper and the YOCO paper. Dust is a biased estimator that prevents the model from being able to learn to generate kvcache beneficial to predicting upcoming tokens. But YOCO architecturally pre-removes this possibility.
1
13
843
This is perhaps half of the full story. Specifically, it splits it into a dust-optimal part (the cross decoder) and a dust-hostile part (the self decoder). Need to do experiments on what should be done here but I think it may lead to a better arch.
1
103
Why does this take two years to build what am I missing, I feel like I could do this in a couple weeks.
We're announcing the public beta of datavendor.ai We spent the last two years building the best solution for people buying and selling data, whether you're a researcher in a lab or a company trying to sell data. Data is the fundamental bottleneck for AI progress, and DataVendor will be the infra that solves it.
5
43
8,573
what if you just shot your infra engineers
12
599
There are many ZO papers with results like this. Many different optimizers which choose directions to perturb in, using one manner of trickery or another. It's pretty obvious that these need to be adapted to Dust, and re-tested. I do not expect the results to move the needle. But it's probably worth setting a bunch of research agents on. The holy grail would be solving it for large networks, in a pretraining context. I think we still do not understand what happens to these loss landscapes to make SPSA-like algorithms fail, and better understanding of what's going on would be huge.
Conventional zeroth-order optimizers such as MeZO estimate gradients through random parameter perturbations, wasting evaluations on directions unrelated to meaningful updates. AGZO from ICML26 exploits a simple but powerful geometric property: the weight gradient of a linear layer lies in the subspace spanned by its input activations. Rather than sampling perturbations across the entire parameter space, it extracts low-rank activation subspaces during forward computation and restricts gradient estimation to those directions. Under spectral concentration assumptions, the authors prove better expected alignment with the true gradient than isotropic perturbations. On Qwen3-0.6B, AGZO achieves 89.2% accuracy on CB versus 80.3% for MeZO, while enabling Qwen3-4B fine-tuning in a hardware setting where full first-order training runs out of memory. The deeper insight is that avoiding backpropagation does not require treating neural networks as structureless black boxes. Forward activations already reveal useful information about optimization geometry, connecting zeroth-order learning with randomized linear algebra and low-dimensional representation structure. However, the method remains substantially more iteration-intensive than first-order training, and its advantages have not been established at frontier pretraining scale. The next question is whether adaptive activation subspaces can reduce both gradient-estimation noise and the number of forward evaluations required for effective learning. Perhaps the next generation of optimizers will use forward computation not merely to evaluate loss, but to determine where parameter updates should occur. arxiv.org/abs/2601.17261
1
18
923
This concurs with my own findings on training looped transformers, by the way. Although their work is much more polished than mine.
Looped transformers often save compute by truncating backpropagation to the last few loops. Is it worth it? We trained ~600 models to find out 👀 Short answer: only if the loop count is fixed. Otherwise, run fewer loops and train them all! 📄 arxiv.org/abs/2610.26030 🧵👇
1
5
684
The Dust paper is really big. A breakthrough. After spending a few days to really digest it though, I'm somewhat disheartened that so much of it is implementation details which are not explained. I'm working on a blog post to reverse engineer the math, methods, and choices.
Backprop has been the only credit assignment algorithm capable of training large neural nets. Introducing Dust, the first zeroth-order method to pretrain transformers to approach and sometimes even *exceed* backprop with large amounts of computation (bitter lesson!) - Dust is on the order of 1,000 to 10,000x more compute efficient than EGGROLL, the state-of-the-art ES method, for training transformers. - We chose pretraining transformers because it's arguably the hardest task possible for zeroth-order optimization. - Search in high dimensions is really misunderstood: zeroth-order usually gets better with overparameterization, not worse, i.e. at a fixed population size, larger models (up to 120x) reach a lower loss than smaller ones. - Backprop-like gradients emerge from a large population of activation perturbations, and the alignment holds up at every scale we tested, up to 1B tokens, which is critical for scaling. The core idea is a *virtual population*, which helps scale to large populations in transformers by perturbing activations in parallel. w/ @bishmdl76, @cs_serdar, @akshayvegesna
8
27
388
19,252
I'm going to be presenting my research at the Latent Space paper club tomorrow, thanks @yikesawjeez. Link: luma.com/k8u3voz2
1
2
1
25
1,094
I love it when this happens
13
35
2
365
8,983