When Training Pipeline Issues Look Like Data Deficiency
During training pipeline issues can manifest themselves as data deficiency from the outside. Here are few things you can do
During training pipeline issues can manifest themselves as data deficiency from the outside. Here are few things you can do
During training a data mixture config will say something like code (data domain) is 10 percent of the run. That number is a plan and it is not what the model actually experiences during training.
When a large training run is slow, the usual dashboard shows GPU utilization, memory used and NVLink traffic per GPU. None of these tells a researcher which parallelism dimension is costing time.
Continuing my thread on agentic systems optimization I found AgentFactory concept interesting. It is a recent paper to optimize the model and the agent workflow together, rather than treating the underlying model as fixed and only searching over prompts or workflow structure.
Suppose a student knows three valid ways to solve a problem. They can use algebra, draw a diagram, or reason through the numbers directly.
A multimodal model has two main parts: encoders that turn images, video, or audio into embeddings, and the LLM backbone, which is the language model that takes those embeddings together with the text tokens and does most of the computation. Memory profile a. The encoder for images, video, or audio is usually small, but long samples create a lot of activation memory.
It was interesting to compare MoE Parallel Folding in Megatron with JAX/TPU architecture. MoE Parallel Folding lets attention layers and MoE layers use different parallelism settings in the same model.
NVIDIA cuObject lets applications read and write S3 compatible object storage directly into GPU memory over RDMA. The concept has strong efficiency promise.
RL post-training for agents (2 of 2) 1. Rollouts and training a. Training and Inference infra can be colocated and same GPUs alternate between generating and training, and weights are resharded between the training layout and the inference layout. b. Colocated GPUs wait on the longest trajectory.
RL post-training for agents (1 of 2) What it takes to post-train a model to operate reliably as an agent. This is a 2 post series.
JEPA models can suffer from representation or embedding collapse. Meaning many different patches of video or images can map to the exactly same embedding space.
One interesting part of V-JEPA 2-AC is how Meta combines teacher forcing with rollout loss. The model learns: visual state + robot state + action → next visual state
Continuing on topic of Cosmos 3.0 I have also been comparing its training infra with some other world models but as a baseline this is the training setup. As I posted earlier the model is a 16B (Nano) or 64B (Super) Mixture-of-Transformers with a Reasoner tower and a Generator tower in every layer.
The Nemotron 3 Ultra technical report has a scaling RL infra section which has very useful and practical lessons learnt. The basic setup 1. Prompts are sent to vLLM for rollout generation
I think there is an opportunity to make low-level GPU and TPU metrics much more useful to model researchers. The profiling systems are already quite good.
One of the interesting talks for me at Ray Summit was vLLM on TPU with TorchTPU and Ray. Layering should be obvious
You can get a 262K context window, GPQA Diamond of 84.3, AIME 2026 of 89.2, LiveCodeBench of 80.0 and MMMU-Pro of 76.9 from Gemma 4 at just 31B parameters. For comparison, Kimi K3 gets 93.5 on GPQA Diamond and 81.6 on MMMU-Pro, but it is a 2.8T parameter MoE model with about 104B parameters active per token and a 1M context window.
Over the last year, a lot of the Kubernetes AI work can look like Kubernetes itself learned to understand GPUs, distributed training and model state. In my observation, the model is more modular.
Lot of discussion on GLM 5.3-Flash built on Chinese domestic chips but my observation has been more focused on continuing trends in model architectures. Full attention at every layer and one-token-at-a-time decoding are both becoming too expensive.
The opportunity with RL-enabled post-training is to build a much more integrated platform across training, inference, data, environments and agents. The post-training loop now includes rollout workers, environments, reward models and verifiers, policy optimization, and continuous evaluation.