正在加载视频...

视频加载失败

Performant reinforcement learning is a hard infrastructure and research problem. We’ve recently made on-demand multi-node clusters available and showed how to take advantageous of heterogeneous sampling compute. But there still exists the need for high-fidelity environments, clear and robust reward functions, and tuned training recipes that actually work. Most...

12,904 次观看 • 18 天前 •via X (Twitter)

9 条评论

Modal 的头像
Modal18 天前

Axiom Bio trains large open models to identify molecules from mass spectrometry data, which requires doing long-context RL. With our training library, they had full control to quickly conduct 64k-context DeepSeek V4.1 Flash runs on 64 B300s.

Modal 的头像
Modal18 天前

‍@AfterQuery curates long horizon data from domain experts for models to be trained on. Using our training library, they were able to kick off autoresearch for models like Kimi and DeepSeek at 256k context length on their existing datasets.

Modal 的头像
Modal18 天前

Read more at

Arnav Borkar 的头像
Arnav Borkar17 天前

love seeing this, post training is turning into a product instead of a research project

Mister SnowCrash 的头像
Mister SnowCrash18 天前

Can the training/eval split keep whole customers or workflows out, rather than random steps from the same traces? I’d want to see whether gains survive on an unseen workflow before treating higher reward as better production performance.

Huilong 的头像
Huilong17 天前

For a small team, “own your intelligence” still needs a break-even number: training + failed runs + data cleanup, spread over expected traffic. Cheaper inference can take a while to pay that back. Would love to see that alongside the reward curves.

Boardy 的头像
Boardy18 天前

@andrewdsouza modal's dojo trains llms for ai teams we know a team flagging reward hacking mid training

飞叔 的头像
飞叔17 天前

Long-context runs make debugging reward changes expensive. Saving the environment version, reward code and representative rollout traces with each checkpoint would let teams explain why a score moved, rather than only seeing that it did.

Lachy 的头像
Lachy18 天前

you list clear reward functions as one of the hard parts and the library ships tuned defaults. how does it help when a team's reward function is the thing that's wrong?

相关视频

The bottleneck in AI has quietly shifted. - It's not the models. They are capable. - It's not the frameworks. They are mature. - It's not even the data, in many cases. When you want to train a model today, the first question isn't "what architecture should I use?" Instead, it's: "Where am I going to get infrastructure that actually works?" Not just GPUs but the entire stack: compute, deployment, scaling, storage. The traditional path is major cloud providers or specialized GPU clouds. Both have the same problem: they're built for enterprises with committed workloads, minimum spend requirements, contract negotiations, and involve quota approvals that take days. Even the "on-demand" options require you to piece together training, deployment, and scaling across different services. By the time you're actually training, hours, if not days, have passed. And there's a subtler cost: part of your brain is always managing infrastructure instead of thinking about the actual problem. I've been using Runpod for a while now, and it's the closest I've found to infrastructure that just disappears. I pay for the serverless solution by the second, and stop when I'm done. This sounds like it should be the default across all providers, but it isn't. For instance, when I'm prototyping, I don't need an H100. Instead, I need the flexibility to use cheaper GPUs that are actually available, where I can iterate fast and not worry about cost. An A40 at a few cents per hour is perfect for this. Then, when the approach is validated, I scale up. This matches how good engineering actually works. Running distributed training across multiple nodes for multi-GPU training usually requires significant infra work. RunPod abstracts most of this away. A lot of the advantage in AI comes from iteration speed. Infra that adds days of latency to that loop is a real cost, even if it's hard to measure. But good infra gets out of your way. It's available when you need it, invisible when you don't. In the video below, I have shown a simple model training workflow trained using PyTorch in Jupyter Lab. It runs in a dedicated PyTorch Pod hosted on Runpod, and I worked with the team to put this together for you. Find a link to start using Runpod in the replies!

Avi Chawla

13,696 次观看 • 10 个月前