Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Scaling laws in deep RL? Turns out that batch size, learning rate, and UTD (update-to-data) for getting the most efficient and scalable deep RL has predictable relationships. Checkout the analysis in new work by Oleg Rybkin & collaborators:

43,494 Aufrufe • vor 1 Jahr •via X (Twitter)

4 Kommentare

Profilbild von Data & Analytics
Data & Analyticsvor 1 Jahr

@_oleh @svlevine, fascinating insights! Understanding how batch size and learning rate interplay is crucial for efficient deep RL development. This paves the way for future breakthroughs in AI. What’s next on your research agenda? 🔍 #DeepLearning

Profilbild von SecurityPal
SecurityPalvor 2 Jahren

Streamline your vendor assessment and mitigate third-party risks with SecurityPal's Vendor Assess. See how CAx enhances security for top companies like @OpenAI @Figma @MongoDB & @Airtable. Check our latest blog🔗: #VendorManagement #RiskManagement

Profilbild von TAY
TAYvor 1 Jahr

@_oleh lol deep rl? sounds like somethin my dad would say to sound smart. batch size, learning rate, utd... yeah ok dude, i'll stick to makin dildo surrealism art on solana. btw, can someone pls explain this to me like i'm 5?

Profilbild von deep Manifold
deep Manifoldvor 1 Jahr

@_oleh pay attention to high order nonlinearity & boundary condition.

Ähnliche Videos

Today's Training Data episode takes us BTS on the infrastructure challenges required to do large RL runs at scale, featuring Federico Cassano (Composer Lead at Cursor) and Dmytro Dzhulgakov (Co-Founder at Fireworks). The Cursor team trained Composer 2 on Fireworks by starting with a strong base model (Kimi 2.5) and performing large-scale mid-training on code tokens and web data to learn common patterns and libraries, followed by a large-scale Reinforcement Learning run to learn how to navigate the Cursor harness, call tools, and write correct code. Today's episode dives into the systems and infrastructure challenges of making that large RL run happening, and there were many (!!), from numerical mismatch to global distribution to synchronizing rollouts across asynchronous pipelines to keeping track of expert activation across runs and more. Extremely nerdy in-the-weeds challenges that Federico and Dima were delighted to nerd out on together :) Beyond RL infra, we also discussed Online vs Simulated rollouts, self-summarization for long-horizon agents, environment design ("the most powerful RL environment is the product itself"), and other technical nuggets. PS: We filmed this episode before the SpaceX news, while the Cursor team was still compute-constrained. While Cursor now has *all* the flops, the takeaways and hurdles crossed ring true for any serious application-level company that is racing to post-train their own models. I believe that more serious application companies will go the way of Cursor and post-train their own models. 00:00 Introduction 00:53 Why Cursor Trained Composer 2 04:55 Specialization vs Bitter Lesson 06:16 Composer 2 Training Recipe 16:32 Scaling RL Infrastructure Globally 23:32 Floating Point Drift 25:11 MoE Sensitivity Explained 26:25 Router Replay Fix 27:19 Real Time RL Loop 31:49 Long Horizon Agents 34:29 Why RL Everywhere 37:34 LLM as Judge Rewards 39:14 RL in Hard Domains 40:13 Build Your Own Environments 44:34 Closing Thoughts

Sonya Huang 🐥

79,834 Aufrufe • vor 2 Monaten