ArXiv

PhyAI: Real-Time Physical AI at the Edge, Scalable Rollouts in the Cloud

Authors
Chenghua Wang, Daliang Xu, Dongqi Cai...
Categories
cs.AI, cs.RO
arXiv
https://arxiv.org/abs/2608.03682v1
PDF
https://arxiv.org/pdf/2608.03682v1

Brief

PhyAI is a unified inference engine for Physical AI that consolidates graph execution, kernels, memory management, and parallel services while putting architecture-specific logic into model adapters. Based on the abstract, the system runs VLA and WAM models across onboard, edge, and cloud, attains 1.40x–4.65x speedups vs. official implementations, halves Cosmos3-Nano-Policy-DROID latency on eight H20 GPUs (2.46→1.18 s), and uses a control-time Roofline to distinguish inference- vs environment-bound control workloads.

Why it matters

PhyAI provides a single unified inference runtime for Physical AI (vision-language-action and world-action models) across onboard, edge, and cloud, using adapter modules for model-specific conditioning; it achieved 1.40x–4.65x speedups versus official implementations of pi0, pi0.5, GR00T N1.7, and MiniCPM-Robot, and the adapter enabled adding MiniCPM-Robot the day it released.

Key details

  • On Cosmos3-Nano-Policy-DROID PhyAI cut latency from 2.46 s to 1.18 s on eight H20 GPUs (CFG=2, TP=4), a 2.08x speedup; authors note specialized runtimes remain faster in some configs and aim for one runtime with competitive latency rather than absolute best in every case.
  • Detailed profiling and a new "control-time Roofline" expose workload differences: on a Hopper GPU at batch size 1 the pi0.5 action expert is 8.8% of FLOPs but 57.2% of latency (dropping to 13.5% of FLOPs and ~100 samples/s at batch 32); Cosmos3 is generation-dominated (only 14.3% throughput gain from batch 1→16). Code and benchmarks: https://github.com/mingti-org/phyai.
Source evidence

Abstract

Physical AI policies require inference throughout their lifecycle, including model evaluation, cloud reinforcement learning rollout, edge GPU serving, and onboard deployment. Although these settings share the same checkpoint and action semantics, they often rely on separate inference programs. To unify them, we build PhyAI, a Physical AI inference engine with a single runtime that keeps architecture-specific conditioning, solver, cache, and output logic in model adapters while sharing graph execution, kernels, memory management, and parallel services. The same codebase runs vision-language-action (VLA) models and world-action models (WAMs) on single or multiple GPUs across onboard, edge, and cloud deployments. We used the adapter interface to add MiniCPM-Robot on the day of its release. PhyAI achieves 1.40x-4.65x speedups over the official implementations of pi0, pi0.5, GR00T N1.7, and MiniCPM-Robot. On Cosmos3-Nano-Policy-DROID it reduces latency from 2.46 to 1.18 s on eight H20 GPUs (CFG=2, TP=4), a 2.08x speedup. Specialized runtimes remain faster in several configurations, so our goal is one runtime with competitive latency rather than the fastest result in every case. Detailed profiles reveal why different models need different execution policies: on a Hopper-series GPU at batch size one, the pi0.5 action expert accounts for 8.8% of FLOPs but 57.2% of latency; at batch size 32 its share drops to 13.5% and throughput reaches about 100 samples/s. Cosmos3 remains generation-dominated and gains only 14.3% throughput as batch size increases from 1 to 16. We further introduce the control-time Roofline, which distinguishes inference-bound from environment-bound control; the measured pi0.5 points on four LIBERO suites are environment-bound while Cosmos3 stays inference-bound. Code and benchmarks: https://github.com/mingti-org/phyai.

Comment: 25 pages, 9 figures