Massively Parallel Sim RL
Isaac Lab, Newton, MJX, and Brax: GPU-parallel environments and the wall-clock economics of training.
- Last reviewed
- Reading time
- 9 min
- Citations
- 8
The four-minute training run from the previous module was not an algorithmic result. PPO was already four years old when Rudin and colleagues used it to train ANYmal to walk in minutes Rudin 2021. What changed between 2021 and 2026 was the infrastructure underneath the algorithm: physics moved onto the GPU, environment counts went from dozens to tens of thousands, and the wall-clock cost of a walking policy collapsed by orders of magnitude. This module is about that infrastructure: what the throughput numbers actually are, and where the remaining bottleneck sits.
The chart below illustrates the cost arithmetic before the history. Drag the parallel environments slider from 64 upward: in the default model, fixed CPU-and-transfer work takes a smaller share of each iteration and the chosen experience budget takes less wall-clock time. This is a constructed comparison, not repeated measurements of one training run.
4,096 envs: 4.0 min to target reward at 924k FPS
At low env counts the fixed per-iteration costs (learning update, host-device transfer, the Python loop) dominate and the GPU idles; at high counts simulation takes over and wall-clock falls from hours to minutes. Diamonds show reported time bounds, not measured equalities. The rough/deployment run used 4,096 robots and an i9-11900k / RTX A6000; the flat diamond x-coordinate is illustrative.
Wall-clock to the target reward falls steeply from 3.6 h at 64 envs to 4.0 min at the current 4,096 envs, then flattens toward 1.5 min at 16,384: simulation draws level with the fixed learn-and-transfer costs near 12,500 envs, between the 8,192 and 16,384 stops, and is the larger bucket beyond, and the flat-terrain time bound (under 4 min) is shown at an illustrative 4,096-env position, not a source-established flat-run environment count.
Sampled wall-clock by parallel environment count
| parallel envs | wall-clock | throughput |
|---|---|---|
| 64 | 3.6 h | 17k FPS |
| 256 | 54.3 min | 67k FPS |
| 1,024 | 14.0 min | 261k FPS |
| 4,096 | 4.0 min | 924k FPS |
| 16,384 | 1.5 min | 2.5M FPS |
The 2021 break: physics moved onto the GPU
Isaac Gym ran an end-to-end GPU accelerated training pipeline for complex robot tasks on a single GPU. PhysX simulated on the GPU and exposed the simulation state directly as PyTorch tensors, so the physics buffers and the policy network never round-tripped through the CPU. The authors report two to three orders of magnitude improvement over the conventional split of a CPU simulator feeding a GPU network Makoviychuk 2021.
Rudin and colleagues report flat-terrain walking policies trained in under four minutes on a single workstation GPU. Separately, their documented simulation-and-deployment policy used 4,096 parallel ANYmal robots, batches of 98,304 RL transitions (24 steps per robot), and 1,500 policy updates in under twenty minutes on an i9-11900k CPU and NVIDIA RTX A6000 GPU. Their game-inspired terrain curriculum promotes robots that cross a tile boundary, demotes those that cover less than half the commanded distance, and returns robots that solve the hardest level to a random level Rudin 2021. The paper links its released training code, legged_gym; the pinned October 2021 repository identifies itself as the Isaac Gym environment used to train ANYmal on rough terrain Rudin 2021.
The massively parallel regime inverts the usual PPO instincts. Rollouts are short (a few dozen steps per environment per iteration, with bootstrapping covering the rest), batches are enormous (on the order of 100k transitions), and the learning rate adapts to a KL-divergence target rather than following a fixed schedule. None of this works at 16 environments; all of it is stable at 4,096.
The JAX line: Brax, MJX, MuJoCo Playground
NVIDIA's stack was not the only path. Brax, from Google in 2021, wrote the physics and the learning algorithms in JAX so both compile onto the same accelerator, training performant policies on MuJoCo-like tasks in minutes Freeman 2021. MuJoCo XLA (MJX) later brought MuJoCo's contact model into that batched-GPU setting, and MuJoCo Playground (2025) packaged it as an open robot-learning framework spanning locomotion and manipulation, with sim-to-real transfer as a stated goal rather than an afterthought Zakka 2025.
What the environment count actually buys
This authored fixed-transitions model is not a benchmark. We choose a budget of 220 million transitions and 24 rollout steps per environment per iteration, with 4,096 environments and the CPU toggle off by default. Each iteration costs 0.02 seconds plus 0.000004 seconds per environment for simulation, 0.04 seconds for learning, and 0.03 seconds for CPU and transfer work. The toggle adds 0.000022 seconds per environment to the CPU bucket. These costs and the fixed budget are illustrative choices, not estimates recovered from either paper. The curve uses 49 logarithmically spaced environment counts from 64 to 16,384, rounded to integers, and sample times rounded to 0.01 minute. Its near-four-minute default is a chosen calibration, not validation by the flat-terrain result. The flat diamond also uses a chosen 4,096-environment position; only the separate rough-run protocol establishes that count.
The CPU toggle illustrates a possible bottleneck; it does not reproduce a measured Isaac Lab curve. In the paper’s state-based Franka cabinet-drawer benchmark, a GeForce RTX 5090 workstation with an AMD 9800X3D CPU approaches a two-GPU RTX PRO 6000 server with two AMD EPYC 9554 CPUs. The authors attribute the task-dependent comparison to CPU bottlenecks in parts of PhysX and the main training loop, together with the workstation’s fast single-core CPU. This is a finding about those systems, not a universal CPU limit
Source: NVIDIA 2025.
How to read this chart
The curve is an illustrative fixed-transitions model, not a benchmark. The diamonds mark reported time bounds: under four minutes for the flat-terrain result and under twenty minutes for the documented 4,096-robot simulation-and-deployment run on an i9-11900k CPU and RTX A6000 GPU. The flat diamond is placed at 4,096 environments for illustration; the inspected paper does not bind that flat result to the detailed rough-run configuration. Neither diamond is a measured equality or validation of this toy curve Rudin 2021.
Isaac Lab and the framework era
The 2025 Isaac Lab v1 paper describes OpenUSD scene graphs, PhysX simulation, RTX rendering, and camera tiling that batches cameras into one render pass. Warp ray-casting supplies height-scanner and LiDAR-like distance queries; those geometric sensors omit photorealistic rendering effects. The framework includes implicit and explicit actuator models, including nonlinear effort limits and learned actuator networks, plus a manager-based environment API and built-in support for RSL-RL, RL-Games, SKRL, Stable-Baselines3, and Ray
Source: NVIDIA 2025.
In the paper’s headless state-based benchmarks, distributed training on RTX PRO 6000 GPUs scales "almost perfectly linearly" over the tested configurations. At the reported eight-GPU, 16,384-environment setting, the DextrAH teacher grasp-and-lift task exceeds 900,000 frames per second and the Franka cabinet-drawer task exceeds 1.6 million. These are environment-learning FPS: environment steps divided by simulation plus learning time, not camera-only FPS or a robot control frequency. The RTX PRO 6000 server uses two AMD EPYC 9554 64-core processors
Source: NVIDIA 2025.
NVIDIA's 2026 overview describes Isaac Lab 3.0 as separating backend-specific code from the core API. Developers can use Isaac Sim with PhysX and RTX for photorealistic, sensor-rich workflows, or run headless Newton physics for high-throughput simulation. The overview also describes adding photoreal sensors through the standalone OVRTX renderer, or using Newton's renderer for vision-based RL with many environments Cano 2026.
Newton: physics as a multi-solver library
NVIDIA's March 16, 2026 release post announces Newton 1.0 GA at GTC 2026 and describes an open-source, GPU-accelerated physics engine built on NVIDIA Warp and OpenUSD. It identifies Newton as a Linux Foundation project founded by NVIDIA, Google DeepMind, and Disney Research. The post calls Isaac Sim 6.0 and Isaac Lab 3.0 early access releases Reist 2026. The later NVIDIA overview describes the engine as differentiable, while noting that differentiation support differs between solvers Cano 2026.
Newton puts multiple solvers behind a unified API. NVIDIA's overview lists MuJoCo and Featherstone for generalized-coordinate articulated rigid bodies; SemiImplicit, XPBD, and Kamino for maximal-coordinate formulations; VBD for rigid bodies, particles, cloth, and soft bodies, with limited joint support; implicit MPM for particle-based continuum materials; and Style3D for cloth Cano 2026. The release post describes Disney Research's Kamino as handling closed-chain mechanisms, and describes coupling VBD and iMPM with MuJoCo Warp for deformable manipulation and locomotion Reist 2026.
The release post describes SDF-based collision built from CAD-exported meshes and hydroelastic contacts inspired by Drake: pressure is distributed across finite-area contact patches rather than isolated points. Its assembly code example precomputes sparse SDFs with narrow_band_range=(-0.01, 0.01), a plus-or-minus 10 mm band around the surface. That band belongs to the example configuration, not a stated engine-wide requirement Reist 2026.
For GPU rack assembly, NVIDIA says Skild AI is training RL policies with Isaac Lab's Newton backend, using SDF collision and hydroelastic contact modeling for tasks including connector insertion. The same post says Samsung "will use Newton" for synthetic data generation to train VLA models and describes Lightwheel's work on calibrated SimReady assets. Its refrigerator-assembly example is a simulated RB-Y1 cable-insertion task using two-way coupled MuJoCo Warp and VBD; the text describes inserting a water-hose connector into its housing Reist 2026. These are NVIDIA's accounts of the workflows, not independently established production-deployment results.
In its MuJoCo 3.5 (MJWarp) release summary, NVIDIA reports speedups over MJX of 252x for locomotion and 475x for manipulation on NVIDIA RTX PRO 6000 Blackwell Series hardware Reist 2026. The post does not specify benchmark task variants, environment counts, numeric precision, or the timing definition for those ratios. Do not read them as end-to-end policy-training-time or control-frequency measurements.
The honest ledger
A few caveats belong with the headline numbers. The Isaac Lab figures come from the framework's own paper, but the hardware, environment counts, and tasks are named, which makes them checkable. The Newton speedups are vendor-reported.
The v1 paper identifies CPU bottlenecks in its tested systems as a target for future releases. For domain randomization, it distinguishes GPU-resident simulation state from physics parameters such as mass, friction, contact offsets, and joint armature, which use PhysX CPU APIs. Most of those parameters can change at runtime; mesh scale and collider type can only be randomized before simulation starts
Source: NVIDIA 2025.
Newton's differentiability is advertised, but its practical use for policy learning, as opposed to system identification and design optimization, is early. Johnny Nuñez Cano and his NVIDIA coauthors call Drake the "gold standard" for contact-implicit trajectory optimisation and rigorous numerics rather than throughput Cano 2026. This is the overview authors' positioning, not a comparative benchmark.
See also
- Why RL Won Locomotion but Not Manipulation
The MDP simulability gap: contact-rich manipulation resists the simulation that made walking routine.
- Sim-to-Real Transfer
Domain randomization, teacher-student distillation, system identification, and real-to-sim correction.
- Reward Design and the MPC Debate
LLM-written rewards and curricula; where classical trajectory optimization still wins.
Linked from
- RL for Robotics
Sample efficiency decides which reinforcement learning algorithms a robot can actually be trained with, from PPO in simulation to offline learning on a fixed dataset.
- Why RL Won Locomotion but Not Manipulation
The MDP simulability gap: contact-rich manipulation resists the simulation that made walking routine.
- Sim-to-Real Transfer
Domain randomization, teacher-student distillation, system identification, and real-to-sim correction.
- Reward Design and the MPC Debate
LLM-written rewards and curricula; where classical trajectory optimization still wins.
- The Data Bottleneck
Robot-hours versus LLM tokens: the log-log reality of embodied data and teleop-farm economics.
References
Nikita Rudin, David Hoeller, Philipp Reist, Marco Hutter, CoRL 2021.
https://arxiv.org/abs/2109.11978
Nikita Rudin, 2021.
https://github.com/leggedrobotics/legged_gym
Viktor Makoviychuk, Lukasz Wawrzyniak, Yunrong Guo, Michelle Lu, Kier Storey, Miles Macklin, David Hoeller, Nikita Rudin, and 3 more, 2021.
https://arxiv.org/abs/2108.10470
C. Daniel Freeman, Erik Frey, Anton Raichuk, Sertan Girgin, Igor Mordatch, Olivier Bachem, 2021.
https://arxiv.org/abs/2106.13281
Kevin Zakka, Baruch Tabanpour, Qiayuan Liao, Mustafa Haiderbhai, Samuel Holt, Jing Yuan Luo, Arthur Allshire, Erik Frey, and 5 more, 2025.
https://arxiv.org/abs/2502.08844
NVIDIA, Mayank Mittal, Yunrong Guo, Pascal Roth, David Hoeller, James Tigue, Antoine Richard, Octi Zhang, and 98 more, 2025.
https://arxiv.org/abs/2511.04831
Philipp Reist, Miguel Zamora Mora, JC Chang, Rishabh Chadha, Mohammad Mohajerani, 2026.
https://developer.nvidia.com/blog/newton-adds-contact-rich-manipulation-and-locomotion-capabilities-for-industrial-robotics
Johnny Nuñez Cano, Mitesh Patel, Asier Arranz, lior ben horin, Raymond Lo, Rishabh Chadha, 2026.
https://huggingface.co/blog/nvidia/state-of-simulation-for-physical-ai
Spot a factual error or missing qualification? Report a content correction.