My opinions are my own

Earth
Joined June 2012
Deep learning is often taught as a sanitized collection of facts and math. But work at the frontier of AI is messy and empirical. Our new class, Deep Learning Alchemy, aims to teach the art and science of deep learning in the hands-on spirit of Language Modeling From Scratch. Students build intuition by running experiments on small LMs, then test it through prediction quizzes: given an unseen code diff, can you predict what happens? deep-learning-alchemy.github… My co-instructor @kothasuhas and I think there's significant demand for classes that treat students as serious learners who want to be assessed for what they’ve learned, and so we're trying a new exam-heavy approach to the class (7 exams, 85% of the grade, with the remaining 15% in-person discussion assessments). We’ve designed the class so students can use AI agents to run their experiments and do their assignment, but they then have to demonstrate that mastery on exams without access to the assignment, and any partial credit on the exam has to come through citations to the assignment, incentivizing them to know what’s in their write-up. The same assignments and quizzes are public for anyone to try (lecture recordings will be released through @StanfordOnline with some delay). We have some very fun assignments and quizzes covering both classic topics (like NQM, run-to-run stochasticity, and scaling laws) and new and timely topics like muP or hyperball. Made by some real experts like @TristanThrush and @wen_kaiyue Try some quizzes below!
43
312
29
2,451
174,200
Check out our latest paper on looped transformers! We found looping enables implicit reasoning, and a new trick we introduced that forces the model to decode the tokens explicitly between looped modules enables the model to learn multi-hop reasoning in a generalizable way!
Frontier labs are rumored to be adopting looped Transformers for their potential to unlock implicit reasoning. But can looped Transformers really master it? We find a bottleneck that keeps looped Transformers from perfect implicit reasoning. Using mechanistic interpretability, we show how looping helps implicit reasoning, why it still struggles to generalize, and how to fix it. We introduce DiscoLoop: a residual design for looped Transformers that improves implicit reasoning. 🧵 Long thread ahead 👇
1
16
102
10,955
We will be teaching Agentic GPU Programming for MLSys as part of the CMU ML Systems course this upcoming spring at @SCSatCMU, touching on knowledge curation, compiler analysis, and feedback loops. We also curated an online book on the topic, check it out mlc.ai/agentic-gpu-programmi…
24
165
8
1,071
80,796
nice mental model :)
Replying to @therealyawpower
Easy, an LRM can do that for you. LRMs have very different training mechanisms and inference behavior. They have very high latency and perform (unrolled) search in natural language program space at test time. They also have radically different performance profiles on any system 2 task.
1
30
Given how many people have tried their hand at NanoGPT, I really didn't expect a 40% reduction in a single go!
New historic NanoGPT record at 39.9s (-27.7s) from @DevenPzak , obliterating the prior record of 67.6s! This record introduces a new paradigm of thinking to NanoGPT: instead of optimizing matmuls or adding more expressive operations, optimize at the individual flop level with incredibly clever engineering and ML judgement. If a flop is low value on a particular step, skip it. Specifically: -(~8s) Sampled softmax. If a token doesn’t appear in a batch, skip its lm_head fwd/bwd some fraction of the time. -Sparse values. Only run an optimizer step for ngram embeddings that occurred in the batch. Set beta1 to zero to enable this. Beta2 is applied retroactively when the row is later used. -Sparse updates. Only update ngram and value embeddings once every 4 steps instead of once every 2. -Sparse communication. Shard the n-gram table across GPUs, and only pass the rows receiving updates on each step. -Sparse optimizer states. For the n-gram table, reduce from 2 floats in Adam optimizer per param, to 1 float per 768 params. -Hand-rolled flash attention for 64 dim heads. There are several additions that add accuracy too: -(~4s) EMA during last 300 steps, combined with lifting final_lr to 0.3 instead of 0.15. -(~1s) A new optimizer, Anvil2, which expands muon via a second tracked momentum buffer, improves the ortho coefficients, and modifies the cautious weight decay application. -A couple additional dynamic skip connections in the network. The most striking consequence of the ‘flop aware paradigm’ is you can grow parameters arbitrarily large, only limited by the available memory, since you can selectively choose how to expend flops on those parameters on each step. NanoGPT has kept active parameters below 124M, but total is unbounded, and has grown to 640M through embedding sparsity over the last year. This PR takes that to its logical conclusion on the 8xH100, scaling up to 65B sparse embedding parameters, which accounts for 25% of the PR’s gains. At frontier scale, where one is not bounded by an 8xH100, one could imagine where this paradigm could lead. github.com/KellerJordan/modd… As this was a very notable PR, I spoke with Deven for an hour to learn how he did it. Here’s his story on the changes: hyperstition.cc/training-nan…
17
26
2
610
73,951
Harvard has put one of the best AI systems curriculums I’ve seen online for free. CS249r goes well beyond model architecture. It gets into the engineering that decides whether a model can actually be trained and served efficiently: processors, memory hierarchy, data movement, accelerators, distributed computation, inference, quantization, serving, reliability and deployment. And there is much more than a textbook. The material includes two open-access ML Systems volumes, TinyTorch for building an ML framework from scratch, interactive browser labs, MLSys·im for experimenting with hardware and infrastructure bottlenecks, StaffML for systems practice, and the lecture slides used for teaching the course. TinyTorch alone has 20 progressive modules. The labs let you change system parameters and see what becomes the bottleneck instead of only reading about it. This is the material I’d study after getting comfortable with neural networks and Transformers. Knowing how attention works is useful. Knowing why KV cache consumes memory, when inference becomes bandwidth-bound, why batching changes throughput, and why adding more GPUs eventually stops scaling is a different skill. Everything is here: mlsysbook.ai/ GitHub: github.com/harvard-edge/cs24…
9
158
3
1,027
41,471
incredibly based that Xiaomi MiMo released their RL dataset link: huggingface.co/datasets/Xiao…
15
104
7
1,242
72,946
Nearly half a year of silence. We spent it studying one problem: how far RL can scale. MiMo-V2.6 is in the middle of its RL run right now. Three things we scaled: compute (~2B tokens per step, 1568 prompts × 16 rollouts, fully async), environments and harnesses (multi-task agentic RL, mixed across multiple harnesses in one run), and grader compute (agentic in-group credit assignment, with test-case and rubric-based rewards). We'll open-source the details piece by piece over the coming weeks. Streaming the run: mimo.xiaomi.com/rl/
424
978
555
9,903
3,132,647
Gaps on why agentic software is fragile Requirements only approximate stakeholder intent, and the model only approximates the real deployment environment. We call these together — requirement gap and model gap. Solution: assurance–revision loop arxiv.org/pdf/2609.12039
15
Yesterday, I was asked about a rumor that Astra openai.com/index/gpt-6-astra… uses a Full Bandwidth Transformer arxiv.org/abs/2608.08888 . I have no special knowledge, but it is at least strange to have someone from OpenAI asking where the idea came from.
18
46
6
451
88,250
I must be among an extremely small group of people (n=1?) that have both 1) trained a frontier LLM and 2) designed and synthesized custom viruses in a lab with my own two hands. And I think that the takes on AI killing us all by creating dangerous viruses is total bogus.
572
1,901
435
14,403
1,953,017
Beginner-friendly LLM course exploring foundations, architectures, training, deployment, and current trends: tinyurl.com/vp844fsm v/@Hesamation
9
212
2
1,184
53,171
《深入理解 AI Infra》开源发布了! 写完《深入理解 AI Agent》后,在与读者交流的过程中,我越来越感到,要开发好基于模型的应用,还需要理解它赖以运行的基础设施。 最近几十年系统领域最重要的变化是编程抽象的上移:从操作系统到模型上下文。传统的操作系统、编译器和硬件要为事先未知的各种程序提供通用能力,系统优化总要在可编程性与性能之间取舍。 如今 LLM 成了最重要的应用,可以针对特定的模型和加速器架构优化;模型设计也开始反过来适应硬件,DeepSeek V4/V4.1 重新设计长上下文的表示方式,就是一例。 从某种意义上说,模型成了 LLM 时代的操作系统,AI Infra 成了 LLM 时代的计算机体系结构。《计算机体系结构:量化研究方法》是我在体系结构领域的入门书,而 AI Infra 领域还缺少一本从硬件约束和模型架构出发、量化推导系统设计的书,这是我写作本书的动机。 全书约 500 页,包括 12 章: 1. 初识 AI Infra 2. 模型架构 3. 推理与训练负载 4. 加速器架构 5. 算子与运行时 6. 超节点 7. 数据中心网络 8. 推理优化 9. 分布式推理 10. 训练系统 11. 资源调度与运行环境 12. 端边云协同 欢迎 star & 提 issue/PR! github.com/bojieli/ai-infra-…
79
597
33
2,933
428,994
分享一份最近收集的 AI Infra 入门阅读清单,建议收藏,慢慢看 AI 已经可以生成很多很好的内容,解释概念、翻译论文、整理资料,都越来越方便。但在这个时代,能静下心来,把一篇好文章认真读完,把没懂的地方再琢磨一遍,我觉得更加难能可贵 这次整理的材料,主要集中在大模型推理这一块。从 KV Cache、显存管理,到请求调度、推理加速,再到怎么判断性能有没有真正变好 做工程的朋友,可以顺着往源码和实验里走。平时看 AI 产业、算力和存储的朋友,也可以先把原理读明白 读文章,挑值得反复读的。 1. 如果只选一篇,我会选 Inside vLLM。 Inside vLLM: Anatomy of a High-Throughput LLM Inference System,作者 Aleksa Gordić aleksagordic.com/blog/vllm 把很多零散的概念串进了一个真实系统:一个请求进来,怎么排队,怎么分配 KV Cache,怎么执行,最后又怎么把结果送回来 PagedAttention、continuous batching、chunked prefill、prefix caching、投机解码、P/D 分离、多卡和性能测试,都能在这条线上找到位置。 这篇适合当主线,后面的材料用来补不懂的地方 2. 想弄懂 continuous batching,先看 Anyscale 这篇。 Continuous Batching 博客 anyscale.com/blog/continuous… llm用户的回答有长有短,有的已经生成完了,有的还在继续。已经空出来的位置,能不能马上接下一个请求? 这篇用静态批处理和连续批处理的对比图,把这个问题讲得很直观。看完你会理解,GPU 的效率,也取决于请求怎么安排 建议重点看图和机制 3. NVIDIA 的两篇,一篇帮你建立全貌,一篇教你怎么看性能。 Mastering LLM Techniques: Inference Optimization developer.nvidia.com/blog/ma… 适合先建立基本认识:处理输入的 prefill 和逐步生成输出的 decode 有什么区别,模型权重和 KV Cache 分别占什么空间,量化、批处理、多卡并行又各自解决什么问题 LLM Inference Benchmarking: Fundamental Concepts developer.nvidia.com/blog/ll… 这一篇我也很推荐。用户等多久才看到第一个 token,后面生成得快不快,整个系统一秒能服务多少请求,是不同的问题。TTFT、ITL、TPOT 这些指标,要连着测试口径一起看 4. 想再往下算一层,读 kipply 的 Transformer Inference Arithmetic Transformer Inference Arithmetic 这是一篇 2022 年的文章。它带你从计算量、内存容量、带宽和通信开销出发,估算推理为什么快、为什么慢,以及 batch size 改变后会发生什么 硬件和模型的具体例子有年代了, 作为 optional 选读
28
268
3
1,012
57,811
We are releasing AutoResearchExam, a benchmark on open-ended machine learning and engineering tasks. Our benchmark covers seven research areas including model training, data curation, AI safety and interpretability. benchmarks.bespokelabs.ai/au… In each task, we give agents 24 hours with a CPU or GPU machine to develop and improve their solutions through experiments and feedback. We measure both speed and quality with a combined score. Our benchmark has a unique feature: testing if agents create improvements that hold up on data they never see. We find that AI research agents often overfit as they try to improve. We see an interesting head-to-head comparison at the frontier: Astra starts the strongest and holds the lead for up to 19 hours but Fable 5.1 catches up and gets the top performing spot in the final hours. Qwen3.8 Max, Gemini 3.8 Flash and Grok 4.6 all sit on the cost-performance Pareto frontier, giving strong options at lower API budgets. Anthropic's Opus and Fable retain nearly all their validation performance on hidden tests, with gaps of 1.1% and 2.9%. Astra's improvement over Sol extends to generalization too, with that gap falling from 6.9% to 1.7%. (1/n)
37
94
16
557
2,034,717
free time this year: CS329Z @ Stanford and CS146 @ CMU CS336 @ Stanford: still in progress. their assignment is a beast!
30
ENOUGH PESSIMISM IN AI PLEASE I feel that we have become unreasonably pessimistic in our field. 1. I keep hearing AI engineers saying we have to make money quickly because there’s only like 2 years left before we’re automated. Depressing. 2. I see a constant obsession with “having a moat”. This is an incredibly sad mental frame. 3. I keep hearing “we have to catch up”. Soulless. And so on. People: Every solution creates the possibility to attack new real problems. We face gargantuan engineering challenges in our world. How to capture carbon? How to get rid of teflon and plastics in water? How to invent batteries that are at least 30 times more efficient? How to solve clean energy? Better solar cells? Better ways of producing clean energy so we stop wars and famine? How to eradicate hundreds of diseases? Cures for addiction? And so on. Real engineering is about being brave and truly attacking the many problems we face, to engage with a true desire to improve the lives of others and our environment. Good engineering is not about protecting your product to make money at the expense of progress (moat thinking). Good engineering is about ensuring your children and grandchildren will be proud of the choices you made in 30 or 50 years. It is about empowering others. It is about advancing science. It is about being one step ahead. Always, one step ahead, meaningfully, proudly. These are great times. Let’s start thinking positively about all the wonderful things we could achieve together.
58
161
29
1,059
114,008