Open Navigation · maintainers of Nav2

The whole robot benchmark, fully loaded.

An independently managed, vendor-agnostic benchmark that compares robotics compute platforms using realistically complex, data intensive, representative mobile robotics applications. A full autonomy stack in a deployment scale environment and an edge AI workload run at the same time, contending for the same CPU, power, and accelerators.

A forklift material handling robot moving pallets, with Nav2 planning, control, and multi-sensor perception plus a VLM for situational awareness on one compute platform.

The same run, from inside

The workload as the robot sees it

We use Nav2 to autonomously navigate the forklift through the warehouse with its advanced, built-in planning, control, behavior modeling, and perception, while it processes multiple 3D lidars, 2D safety lidars, RGBD cameras, and internal sensors. Gemma 4.0 runs alongside it on the same GPU for situational awareness.

Each of these is a real consumer of CPU, memory bandwidth, and accelerated compute on the platform under test. They interact when composed into a full system which this benchmark captures in full.

Click either video to watch it at full length.

Why this benchmark exists

Many benchmarks exist from both hardware vendors and community members, but nearly all focus on evaluating a particular component or algorithm in isolation. Often times, multiple of these algorithms need to be run together which may interact negatively when composed into a full system due to sharing of limited CPU/power or conflicts accessing accelerated computing resources (GPU, NPU, FPGA, etc).

This project fills the gap with a reproducible, independent benchmark for comparing compute solutions for robotics or physical AI applications in all of their complexity. A platform that wins every microbenchmark can still fail to hold a 30 Hz control loop once planning, perception, sensor drivers, and a VLM are all running simultaneously on it at once. That interaction and potential failure mode is what this benchmark measures and seeks to expose.

What is running

Nav2 autonomously navigates a forklift material handling robot within a 200,000 sqft (18,600 m²) industrial warehouse. It moves pallets from shipping/receiving to shelving units while processing multiple 3D lidars, 2D safety lidars, RGBD cameras, and internal sensors. This workload is representative of dozens of companies and tens of thousands of robots deployed today in production environments.

Alongside it, Gemma 4.0, a popular VLM, exercises the platform's GPU. It is integrated into the navigation behavior tree for scene understanding, so its answers actually affect the robot's decisions.

Full methodology →

How it is measured

An external computer runs the simulation; the platform under test runs everything else for compute platform HIL, including simulated driver loads.

Hardware-in-the-loop benchmark architectureA developer computer runs the Gazebo warehouse simulation and the robot's simulated sensors in a Docker container. It is connected over wired Ethernet, carrying DDS traffic, to the compute platform under test. That platform runs the Nav2 autonomy stack, the vision-language model workload, a simulated sensor-driver load, and the metrics capture script, each in its own container.Developer ComputerGazebo SimulationDocker containerSimulated Sensors3x 3D LiDAR · 3x RGBD2x 2D safety LiDARRGB camera · IMUWired Ethernet(DDS)HIL Compute Platform Under TestNav2 AutonomyPlanning · control · perceptionVLM WorkloadGemma 4.0 via llama.cppSensor Driver LoadMeasured on real hardwareMetrics Capture1 Hz system countersMission dispatcherForklift AMR moving pallets in a 200,000 sqft warehouseAll four workloads contend for the same CPU, power, and accelerators

Platforms evaluated

Three platforms in this edition. The benchmark is built to grow. See adding a platform.

FeatureX100 / Strix HaloJetson ThorJetson AGX Orin
CPU16x Zen 5 (32T) @ 5.1 GHz14x Arm Neoverse V3AE @ 2.6 GHz12x Arm Cortex-A78AE @ 2.2 GHz
GPU architectureRDNA 3.5BlackwellAmpere
NPU / DLAXDNA 2 (50 TOPS)None2x NVDLA 2.0
RAMUp to 128 GB LPDDR5X128 GB LPDDR5X64 GB LPDDR5
Memory bandwidth256 GB/s273 GB/s204.8 GB/s
Power (TDP)45-120 W40-130 W15-60 W

Full hardware and as-tested comparison →

Platform balance

Six dimensions, each min-max normalized against the strongest platform in this category.

Data table (3 rows)
Normalized 0–1 against the best platform on each axis; higher is better.
PlatformCPU HeadroomCPU CapabilityGPU CapabilityMemory CapabilityMemory HeadroomClock Speed
AMD Strix Halo1.001.001.001.001.001.00
NVIDIA Jetson Thor0.610.330.940.990.540.75
NVIDIA Jetson Orin0.080.310.150.500.320.83

Source: max_power/amd_strix_halo, max_power/jetson_thor, max_power/jetson_orin · CSV CSV CSV

Add a platform to the benchmark

This comparison covers some of the main robotics compute platforms from major suppliers. It is not a complete map of the robotics compute landscape and it is meant to grow.

Hardware vendors

If you build compute modules for robotics, Open Navigation can bring your platform up, profile it, and include it in this benchmark results reports. Contact us for more information and support.

Contact Open Navigation

Run it yourself

The pipeline is public, designed to be extended, and ran independently. Run it yourself with our instructions with our robotics workload or your own on any platform easily.

Run it

Need ROS 2 or Nav2 help?

Open Navigation maintains Nav2 and provides commercial engineering support: autonomy integration, performance work, and hardware platform bring-up and evaluation.

info@opennav.org Commercial support