Skip to content
Search models or paste a model link. Press Enter to search.

Alpamayo 2 Edge

nvidia/Alpamayo2-Edge
nvidia/alpamayo2-edge architecture graph
nvidia/alpamayo2-edge architecture graph
  • nvidia/Alpamayo2-Edge
  • INT8 / FP16
  • AGX Orin
Labels
  • Image
  • Text
  • VLA
Build
Embedl-optimized, 3 decisions/s
Precision
INT8 / FP16
Runtime
TensorRT Edge-LLM 0.10.1 with Embedl optimizations
Inputs
All 22 camera frames, NVIDIA's released weights
Trajectory
6.4 s
Run Alpamayo 2 Edge on AGX Orin

Alpamayo 2 Edge is NVIDIA's vision-language-action model for autonomous driving.

Methodology

  • Latency: Jetson AGX Orin 64 GB (MAXN) running this build and its server on the 16 drives below, 100 decisions each, back to back; the first 10 of each drive are left out (1440 decisions). Latency, model: camera frames to trajectory, as the server reports it (median 341.4 ms, p90 344.7 ms; per-drive medians 340.9 to 344.4 ms). Throughput, model: 1000 / (the mean model time plus the mean work the server does between decisions). Latency, end to end: request sent to reply received on the device, request decoding included (median 346.1 ms). Throughput, end to end: decisions answered per second, back to back, on the same 16 drives. The model reads all 22 camera frames at NVIDIA's resolutions. Images older than the newest frame are encoded once and reused, so a decision encodes the 6 newest images. In live use the board keeps up with about 2 decisions per second: with one decision every 0.5 s and nothing encoded ahead, camera frame to plan measured 453.2 ms median (534.6 ms p90). The reasoning in words is refreshed after the reply and used by the next decisions, so it does not add to the latency. INT8, except the last two language-model layers, which stay FP16 to keep the reasoning.
  • Accuracy: minADE6 at 5 s: the closest of 6 sampled trajectories, average error over 5 s, on 189 held-out PhysicalAI-AV validation clips, 2 seeds. Embedl on the device, NVIDIA BF16 on an H200, same clips. Embedl is 0.5 % higher (95 % CI -7.4 to +8.1 %); parity is not shown. Measured with the reasoning decoded for each decision; the asynchronous refresh used on the device reuses a reasoning from 0.1 to 0.2 s earlier, which did not change accuracy on 2,000 other validation clips (BF16, PyTorch: -1.0 %, 95 % CI -2.3 to +0.3 %).
  • Power and memory: Power: the board's power rails (tegrastats, every 200 ms) while it decides back to back. Energy per decision: that mean power times the median model time. Idle: the board at rest. Peak memory: the board's RAM in use at the peak, minus before the model started; the GPU shares this memory.
  • Size: The runtime container image and the model files on disk.
  • TensorRT Edge-LLM FP16: NVIDIA's released weights in FP16 with all 22 camera frames, on the same runtime and device, without Embedl's quantization. Shown for speed.
  • NVIDIA PyTorch BF16: NVIDIA's released code (NVlabs/alpamayo2-edge) and BF16 weights (nvidia/Alpamayo2-Edge), on an H200. Shown for accuracy.

Files

Image Size

Model

docker.io/embedl/models:hf.nvidia.alpamayo2-edge.int8-a2e-ga.agx-orin.202611112124b38d

3.39 GiB

Runtime

docker.io/embedl/models:alpamayo2.orin-a2e-ga.runtime.arm64.20261111160169da

0.96 GiB

Variants

Every build of Alpamayo 2 Edge on AGX Orin.

Variant Precision Speed Peak memory Runtime

huggingface_int8_embedl_tensorrt-edgellm

INT8 / FP16 341.4 ms
Latency: Latency, model (camera frame to plan)
4.83 GiB
TensorRT Edge-LLM 0.10.1 with Embedl optimizations
alpamayo2.orin-a2e-ga.runtime.arm64.20261111160169da

huggingface_int8_embedl-10hz_tensorrt-edgellm

INT8 / FP16 10.3 Hz
Latency: Throughput, model
8.59 GiB
TensorRT Edge-LLM 0.10.1 with Embedl optimizations
alpamayo2.orin-a2e-ga.runtime.arm64.20261111160169da

Contact

Peter Kristiansen

Peter Kristiansen

Head of Business Development

Need Alpamayo tailored to your use case?

The download gets you started. For production, we offer a trainable version of the optimized model, so you can fine-tune it on your own data.

We are also happy to help you customize the model for your hardware, your sensors and your driving or robotics scenarios.

Talk to Peter on our sales team to get access and discuss your needs.

Contact sales