Instructions to use nvidia/Cosmos3-Edge-FP8 with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Cosmos
How to use nvidia/Cosmos3-Edge-FP8 with Cosmos:
# No code snippets available yet for this library. # To use this model, check the repository files and the library's documentation. # Want to help? PRs adding snippets are welcome at: # https://github.com/huggingface/huggingface.js
- Notebooks
- Google Colab
- Kaggle
Consolidate FP8 performance benchmarks by hardware
Browse filesReplace the detailed performance tables with one single-GPU Cosmos3-Edge-FP8 table covering 480p generator throughput, reasoner TTFT and output-token throughput, and 32-action policy throughput.
Generator throughput uses 121 frames divided by end-to-end server inference time. Reasoner results use concurrency 1, 50 input text tokens plus a 30-second video sampled at FPS 1, and 100 output tokens. Notes identify the RTX PRO 6000 CUDNN_ATTN exception, T3000 emulation, and Orin weight-only W8A16 execution of the FP8 checkpoint.
Policy results remain unavailable because the supplied measurements use a different runtime and action chunk size. Other unavailable configurations are shown as dashes. No estimates are included.
Validation: checked model, precision, one-GPU scope, workloads, calculations, rounding, and table structure; git diff --check passes. Unrelated README content is preserved. This PR changes only README.md and starts from current main with one new commit.
|
@@ -294,144 +294,32 @@ All models are evaluated on image-to-video generation at **480p, 24 fps**. Throu
|
|
| 294 |
|
| 295 |
The Edge model is a strong initialization for downstream action tasks. For example, post-training it on the DROID dataset produces a policy whose RoboLab success rate is reported in the [Cosmos3-Edge-Policy-DROID model card](https://huggingface.co/nvidia/Cosmos3-Edge-Policy-DROID#robolab).
|
| 296 |
|
| 297 |
-
###
|
| 298 |
|
| 299 |
-
The
|
| 300 |
|
| 301 |
-
|
| 302 |
-
|
| 303 |
-
All results were measured using a single GPU and a batch size of 1.
|
| 304 |
-
|
| 305 |
-
#### Generator
|
| 306 |
-
|
| 307 |
-
Unless otherwise noted, visual-generation benchmarks use **480p resolution**. Image-to-video benchmarks generate **189 frames**.
|
| 308 |
-
|
| 309 |
-
##### vLLM-Omni
|
| 310 |
-
|
| 311 |
-
| GPU or Platform | Image-to-Video | Forward Dynamics | Inverse Dynamics | Policy DROID |
|
| 312 |
-
| --- | ---: | ---: | ---: | ---: |
|
| 313 |
-
| B200 SXM 192 GB | — | 2.44 s | 3.98 s | 0.99 s |
|
| 314 |
-
| H100 SXM 80 GB | 27.64 s | 3.91 s | 5.60 s | 1.41 s |
|
| 315 |
-
| H100 NVL 96 GB | 35.60 s | 4.73 s | 6.39 s | 1.37 s |
|
| 316 |
-
| H20 SXM 96 GB | 108.16 s | 12.77 s | 15.49 s | 3.41 s |
|
| 317 |
-
| RTX PRO 6000 Blackwell Server Edition | 36.29 s | 5.65 s | 7.46 s | 1.87 s |
|
| 318 |
-
| DGX Station | 12.17 s | 4.33 s | 6.34 s | 8.11 s |
|
| 319 |
-
| DGX Spark | 165.96 s | 26.43 s | 30.86 s | 7.66 s |
|
| 320 |
-
| Jetson AGX Thor T5000, 128 GB, MAXN | 137.50 s | 6.05 s | 7.19 s | 6.32 s |
|
| 321 |
-
| Jetson T3000, 32 GB, 1100 MHz | 194.76 s | 8.67 s | 10.25 s | 8.63 s |
|
| 322 |
-
| Jetson T2000, 16 GB, 702 MHz, THOR_NANO | 101.20 s | — | — | — |
|
| 323 |
-
|
| 324 |
-
##### PyTorch
|
| 325 |
-
|
| 326 |
-
| GPU or Platform | Image-to-Video | Forward Dynamics | Inverse Dynamics | Policy DROID |
|
| 327 |
| --- | ---: | ---: | ---: | ---: |
|
| 328 |
-
| H100
|
| 329 |
-
|
|
| 330 |
-
| H20
|
| 331 |
-
|
|
| 332 |
-
| DGX
|
| 333 |
-
|
|
| 334 |
-
|
|
| 335 |
-
| Jetson
|
| 336 |
-
|
| 337 |
-
|
| 338 |
-
|
| 339 |
-
|
| 340 |
-
|
| 341 |
-
|
| 342 |
-
- **
|
| 343 |
-
- **
|
| 344 |
-
- **
|
| 345 |
-
|
| 346 |
-
|
| 347 |
-
|
| 348 |
-
These measurements use the `nvidia/Cosmos3-Edge-FP8` checkpoint with one GPU. Metrics were collected at client-side concurrency levels of 1, 64, 128, and 256.
|
| 349 |
-
|
| 350 |
-
The workload notation is **input sequence length / output sequence length / video FPS**.
|
| 351 |
-
|
| 352 |
-
###### RTX PRO 4500 Blackwell Server Edition
|
| 353 |
-
|
| 354 |
-
| Input / Output / Video FPS | Metric | Concurrency 1 | Concurrency 64 | Concurrency 128 | Concurrency 256 |
|
| 355 |
-
| --- | --- | ---: | ---: | ---: | ---: |
|
| 356 |
-
| 50 / 1 / 1 | Time To First Token (ms) ↓ | 165.79 | 8817.33 | 14702.20 | 29482.39 |
|
| 357 |
-
| | Request Latency (ms) ↓ | 165.79 | 8817.33 | 14702.20 | 29482.39 |
|
| 358 |
-
| | Request Count (requests) | 50 | 320 | 256 | 512 |
|
| 359 |
-
| | Request Throughput (req/s) ↑ | 6.00 | 6.55 | 6.55 | 6.52 |
|
| 360 |
-
| | Output Token Throughput (tok/s) ↑ | 6.00 | 6.55 | 6.55 | 6.52 |
|
| 361 |
-
| 50 / 1 / 2 | Time To First Token (ms) ↓ | 371.67 | 20375.98 | 33812.45 | 68201.55 |
|
| 362 |
-
| | Request Latency (ms) ↓ | 371.67 | 20375.98 | 33812.45 | 68201.55 |
|
| 363 |
-
| | Request Count (requests) | 50 | 313 | 249 | 492 |
|
| 364 |
-
| | Request Throughput (req/s) ↑ | 2.68 | 2.77 | 2.76 | 2.71 |
|
| 365 |
-
| | Output Token Throughput (tok/s) ↑ | 2.68 | 2.77 | 2.76 | 2.71 |
|
| 366 |
-
| 50 / 100 / 1 | Time To First Token (ms) ↓ | 166.86 | 6900.90 | 19625.83 | 45729.55 |
|
| 367 |
-
| | Request Latency (ms) ↓ | 764.15 | 16667.01 | 29196.84 | 55749.62 |
|
| 368 |
-
| | Request Count (requests) | 50 | 320 | 256 | 512 |
|
| 369 |
-
| | Request Throughput (req/s) ↑ | 1.31 | 3.73 | 3.74 | 3.70 |
|
| 370 |
-
| | Output Token Throughput (tok/s) ↑ | 130.63 | 372.40 | 373.98 | 369.87 |
|
| 371 |
-
| 50 / 100 / 2 | Time To First Token (ms) ↓ | 374.93 | 23526.65 | 47550.99 | 101553.31 |
|
| 372 |
-
| | Request Latency (ms) ↓ | 1041.29 | 33712.54 | 57641.53 | 111895.20 |
|
| 373 |
-
| | Request Count (requests) | 50 | 320 | 256 | 512 |
|
| 374 |
-
| | Request Throughput (req/s) ↑ | 0.96 | 1.79 | 1.79 | 1.78 |
|
| 375 |
-
| | Output Token Throughput (tok/s) ↑ | 95.74 | 178.73 | 178.89 | 178.15 |
|
| 376 |
-
|
| 377 |
-
###### RTX PRO 6000 Blackwell Server Edition
|
| 378 |
-
|
| 379 |
-
| Input / Output / Video FPS | Metric | Concurrency 1 | Concurrency 64 | Concurrency 128 | Concurrency 256 |
|
| 380 |
-
| --- | --- | ---: | ---: | ---: | ---: |
|
| 381 |
-
| 50 / 1 / 1 | Time To First Token (ms) ↓ | 141.99 | 3213.91 | 5384.51 | 10792.72 |
|
| 382 |
-
| | Request Latency (ms) ↓ | 141.99 | 3213.91 | 5384.51 | 10792.72 |
|
| 383 |
-
| | Request Count (requests) | 50 | 320 | 254 | 512 |
|
| 384 |
-
| | Request Throughput (req/s) ↑ | 6.96 | 18.00 | 17.95 | 17.89 |
|
| 385 |
-
| | Output Token Throughput (tok/s) ↑ | 6.96 | 18.00 | 17.95 | 17.89 |
|
| 386 |
-
| 50 / 1 / 2 | Time To First Token (ms) ↓ | 239.86 | 7483.22 | 12552.69 | 25259.11 |
|
| 387 |
-
| | Request Latency (ms) ↓ | 239.86 | 7483.22 | 12552.69 | 25259.11 |
|
| 388 |
-
| | Request Count (requests) | 49 | 303 | 249 | 491 |
|
| 389 |
-
| | Request Throughput (req/s) ↑ | 4.06 | 7.28 | 7.49 | 7.34 |
|
| 390 |
-
| | Output Token Throughput (tok/s) ↑ | 4.06 | 7.28 | 7.49 | 7.34 |
|
| 391 |
-
| 50 / 100 / 1 | Time To First Token (ms) ↓ | 138.74 | 943.46 | 2680.17 | 11599.63 |
|
| 392 |
-
| | Request Latency (ms) ↓ | 503.44 | 6188.90 | 13022.07 | 26388.89 |
|
| 393 |
-
| | Request Count (requests) | 50 | 320 | 256 | 512 |
|
| 394 |
-
| | Request Throughput (req/s) ↑ | 1.98 | 10.27 | 9.57 | 8.95 |
|
| 395 |
-
| | Output Token Throughput (tok/s) ↑ | 197.75 | 1026.14 | 956.47 | 893.91 |
|
| 396 |
-
| 50 / 100 / 2 | Time To First Token (ms) ↓ | 239.24 | 1798.96 | 11644.84 | 33293.32 |
|
| 397 |
-
| | Request Latency (ms) ↓ | 638.71 | 13599.89 | 26299.90 | 49165.91 |
|
| 398 |
-
| | Request Count (requests) | 50 | 320 | 256 | 512 |
|
| 399 |
-
| | Request Throughput (req/s) ↑ | 1.56 | 4.66 | 4.50 | 4.45 |
|
| 400 |
-
| | Output Token Throughput (tok/s) ↑ | 155.93 | 465.28 | 449.57 | 444.17 |
|
| 401 |
-
|
| 402 |
-
##### Embedded-platform eager Transformers benchmarks
|
| 403 |
-
|
| 404 |
-
These preliminary measurements use raw Hugging Face Transformers in eager mode rather than vLLM. They are presented separately because their runtime, workload, and metric definitions differ from the vLLM serving benchmarks above.
|
| 405 |
-
|
| 406 |
-
| Board | Specification | Input | Prompt Tokens | Prefill Throughput | Prefill Latency | Decode Throughput | E2E Latency |
|
| 407 |
-
| --- | --- | --- | ---: | ---: | ---: | ---: | ---: |
|
| 408 |
-
| Jetson AGX Thor T5000 | 128 GB / MAXN | Text | 1705 | 8717 tok/s | 0.20 s | 37.3 tok/s | 3.60 s |
|
| 409 |
-
| Jetson AGX Thor T5000 | 128 GB / MAXN | Image | 911 | 4845 tok/s | 0.19 s | 42.6 tok/s | 3.17 s |
|
| 410 |
-
| Jetson AGX Thor T5000 | 128 GB / MAXN | Video | 1263 | 6032 tok/s | 0.21 s | 41.8 tok/s | 3.25 s |
|
| 411 |
-
| Jetson AGX Thor T4000 | 64 GB / MAXN, 1530 MHz | Text | 1705 | 6519 tok/s | 0.26 s | 34.1 tok/s | 3.99 s |
|
| 412 |
-
| Jetson AGX Thor T4000 | 64 GB / MAXN, 1530 MHz | Image | 911 | 3471 tok/s | 0.26 s | 40.3 tok/s | 3.41 s |
|
| 413 |
-
| Jetson AGX Thor T4000 | 64 GB / MAXN, 1530 MHz | Video | 1263 | 4164 tok/s | 0.30 s | 38.1 tok/s | 3.64 s |
|
| 414 |
-
| Jetson Thor T3000 | 32 GB / 1100 MHz | Text | 1705 | 5230 tok/s | 0.33 s | 29.7 tok/s | 4.61 s |
|
| 415 |
-
| Jetson Thor T3000 | 32 GB / 1100 MHz | Image | 911 | 2710 tok/s | 0.34 s | 36.3 tok/s | 3.83 s |
|
| 416 |
-
| Jetson Thor T3000 | 32 GB / 1100 MHz | Video | 1263 | 3388 tok/s | 0.37 s | 33.7 tok/s | 4.14 s |
|
| 417 |
-
| Jetson Thor T2000 | 16 GB / 702 MHz, THOR_NANO | Text | 1705 | 2355 tok/s | 0.72 s | 15.7 tok/s | 8.80 s |
|
| 418 |
-
| Jetson Thor T2000 | 16 GB / 702 MHz, THOR_NANO | Image | 911 | 1233 tok/s | 0.74 s | 19.6 tok/s | 7.21 s |
|
| 419 |
-
| Jetson Thor T2000 | 16 GB / 702 MHz, THOR_NANO | Video | 1263 | 1543 tok/s | 0.82 s | 18.0 tok/s | 7.87 s |
|
| 420 |
-
| Jetson AGX Orin | 64 GB | Text | 1705 | 3260 tok/s | 0.52 s | 12.3 tok/s | 10.83 s |
|
| 421 |
-
| Jetson AGX Orin | 64 GB | Image | 911 | 1840 tok/s | 0.50 s | 12.3 tok/s | 10.81 s |
|
| 422 |
-
| Jetson AGX Orin | 64 GB | Video | 1263 | 2103 tok/s | 0.60 s | 12.2 tok/s | 10.97 s |
|
| 423 |
-
|
| 424 |
-
**Benchmark notes**
|
| 425 |
-
|
| 426 |
-
- All Generator measurements use one GPU or one integrated computing platform.
|
| 427 |
-
- Generator values are average end-to-end or generation latency in seconds; lower is better.
|
| 428 |
-
- Unless otherwise specified, visual-generation measurements use **480p resolution**.
|
| 429 |
-
- Image-to-video measurements generate **189 output frames**.
|
| 430 |
-
- Jetson AGX Thor T5000 and Jetson T3000 visual-generation measurements use **832 × 480** resolution.
|
| 431 |
-
- Jetson T2000 visual-generation measurements use **448 × 256** resolution and therefore should not be compared directly with the 480p results. Its image-to-video values are warm-run measurements generating 189 frames.
|
| 432 |
-
- PyTorch Generator values report average generation latency rather than diffusion-only latency.
|
| 433 |
-
- Datacenter and enterprise forward- and inverse-dynamics results use the autonomous-driving (`AV`) configuration.
|
| 434 |
-
- Jetson AGX Thor T5000 and Jetson T3000 forward-dynamics, inverse-dynamics, and policy measurements use the DROID configuration with action chunk `[16, 8]`.
|
| 435 |
|
| 436 |
## Usage
|
| 437 |
|
|
|
|
| 294 |
|
| 295 |
The Edge model is a strong initialization for downstream action tasks. For example, post-training it on the DROID dataset produces a policy whose RoboLab success rate is reported in the [Cosmos3-Edge-Policy-DROID model card](https://huggingface.co/nvidia/Cosmos3-Edge-Policy-DROID#robolab).
|
| 296 |
|
| 297 |
+
### Performance Benchmarks
|
| 298 |
|
| 299 |
+
The table reports single-GPU inference performance for Cosmos3-Edge-FP8 using FLASH_ATTN unless otherwise noted.
|
| 300 |
|
| 301 |
+
| Hardware | Generator — 480p (frames/s) | Reasoner — time to first token (ms) | Reasoner — output token throughput (tokens/s) | Action Policy — 480p (actions/s, 32-action chunks) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 302 |
| --- | ---: | ---: | ---: | ---: |
|
| 303 |
+
| H100 | 13.04 | 108.1 | 312.64 | - |
|
| 304 |
+
| H200 | 12.96 | 103.0 | 341.18 | - |
|
| 305 |
+
| H20 | 3.29 | 163.6 | 262.42 | - |
|
| 306 |
+
| DGX Station | - | - | - | - |
|
| 307 |
+
| DGX Spark | - | - | - | - |
|
| 308 |
+
| RTX PRO 6000 | 7.52 | - | - | - |
|
| 309 |
+
| RTX PRO 5000 | - | - | - | - |
|
| 310 |
+
| Jetson Thor T5000 | - | 205.7 | 76.69 | - |
|
| 311 |
+
| Jetson T3000 | - | 384.3 | 62.16 | - |
|
| 312 |
+
| Jetson T2000 | - | - | - | - |
|
| 313 |
+
| Jetson AGX Orin | - | 817.8 | 41.46 | - |
|
| 314 |
+
|
| 315 |
+
A dash (-) indicates unavailable benchmark results for the specified configuration.
|
| 316 |
+
|
| 317 |
+
- **Generator:** FP8 image-to-video (`i2v`) with vLLM-Omni, 832 × 480 resolution, 121 generated frames, 35 denoising steps, concurrency 1, and one warmup request. Throughput is 121 divided by end-to-end server inference time in seconds and measures inference throughput. The reported times are 9.277 s (H100), 9.339 s (H200), 36.744 s (H20), and 16.085 s (RTX PRO 6000).
|
| 318 |
+
- **Reasoner:** FP8 vLLM with concurrency 1, 50 input text tokens plus a 30-second, 374 × 374 video sampled at FPS 1 (30 frames), and 100 output tokens. Both metrics use this workload and FLASH_ATTN; output throughput copies the reported output-token throughput.
|
| 319 |
+
- **Action Policy:** FP8 PyTorch, Policy Robot (DROID), 480p, one GPU, and 32-action chunks. Throughput is 32 divided by average generation time in seconds, reported in actions per second.
|
| 320 |
+
- **Hardware:** Generator measurements use one H100 SXM 80 GB, H200 SXM 141 GB, or H20 SXM 96 GB GPU. The documented container default is FLASH_ATTN on these Hopper GPUs. The RTX PRO 6000 generator measurement uses one RTX PRO 6000 Blackwell Server Edition GPU with CUDNN_ATTN.
|
| 321 |
+
- **Embedded hardware:** Reasoner measurements use one integrated GPU: Jetson AGX Thor T5000 (128 GB), a T5000 devkit configured to emulate T3000 (12 SMs, 8 CPUs, 32 GB), and Jetson AGX Orin (64 GB), all in MAXN mode with clocks locked. Orin runs the FP8 checkpoint with weight-only W8A16 compute; Thor uses FP8 compute. T3000 results are emulated measurements. Hardware variants for other rows require matching benchmark results.
|
| 322 |
+
- Throughputs are calculated before rounding to two decimal places; time to first token is displayed to one decimal place. No estimates are included.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 323 |
|
| 324 |
## Usage
|
| 325 |
|